Hello, all. I'm running a rooted At+t locked dell streak. I've install ROM Manager and "Successfully" flashed Clockwordmod several times. However, every time i try to use it (Boot into recovery mode, for instance) it will just reboot, as if you didn't ask. More over, when I try to access it normally (pressing both volume buttons on boot) it launches into stock recovery mode (with the four options - Factory reset, install from pkg, etc).
What should I do?
Stock firmwares automatically replace the recovery image on boot every time, you need to be on a custom rom for it to not do that
Silly me, I was trying to boot into the Clockworkmod recovery mode so that I could install a custom rom...how do I go about circumventing this?
use fastboot -i 0x413c reboot (after installing the recovery)
as it's rebooting IMMEDIATELY hit vol up+down + power, if you hit the dell logo, repeat it because you're too late
if you hit it fast enough, you can use cwm/streakmod once on stock (it'll still overwrite it with stock recovery after reboot)
The ROM Manager app doesn't play well with the Streak.
I recommend Streakmod recovery. I use this version.
If you aren't installing a custom ROM you can make a custom recovery stick by renaming install-recovery.sh to something else (IE - install-recovery.sh.norun). On my phone I found the file in /etc and /system/etc , you would need a root explorer or other root method to do this.
It appears I am more noobish than I had originally considered. Is there a step by step guide to installing a recovery mod? For instance, I am not sure what relevance "fastboot -i 0x413c reboot" has here. Is this something I should type in, and if so, where and under what circumstances?
Thanks!
This streakdroid guide may help.
You flash the recovery image with fastboot and the command to reboot that was in a previous post lets you restart the phone without pulling the battery.
What exactly is on your phone now? Menu->Settings->About phone
Example attached.
On the stock roms go to /system/etc and rename install-recovery.sh to install-recovery.sh.bak (or delete it if you would like) and then whatever recovery you flash will persist after a reboot
Ok here is the situation
I had BoS installed. I nv flashed, installed Flashback. Everything was working fine. I had the standard recovery. So I wanted to install CWM recovery. Downloaded the 1.2 update.zip and put it in the root of the internal SD with the recovery folder.
I started up, seemed like the update applied. Then the tablet booted up normally perfectly fine. BUT now whenever I try to go into recovery, I get the birds, then "Recovery key detected" "Booting recovery kernel image". Then nothing. It just waits there. Still boots up normally fine.
Is there any way to fix the recovery mode without nv flashing again and loosing all the app installs I've done?
TIA
You can nvflash just the recovery partition or use ADB to flash it.
Instructions for doing that are on the BoS first post.
Edit: According to the changelog for flashback it has Roebeet's recovery pack built in.
Open a terminal emulator on the tablet.
Type "su" without the quote and tap enter.
Grant the terminal app superuser rights
Use one of the following commands...
fixrecovery.sh (for stock recovery)
cwmrecovery.sh (for ClockworkMod)
You might need to navigate to /system/bin if the commands are not recognized in the default directory.
Awesome. Worked like a charm.
I have a UK-bought SGT10.1, which I rooted shortly after purchase and installed CWM Recovery using Odin. I've been running In Paris for a while, and was about to update to v5. Last time I downloaded pershoot's kernel from droidbasement, I saw an updated version of CWM Recovery here: http://droidbasement.com/db-blog/?p=2370.
Being a security-type, running the latest versions is always the best option to me - and seeing I know my way around the console I figured I'll install adb/fastboot and use that this time instead of Odin. So I downloaded the SDK, installed the Tab 10.1 drivers (I've reinstalled Windows since I rooted), and grabbed the fastboot .exe from the previous revision and placed it inside android-sdk\platform-tools next to adb.
Now I'm trying to follow the instructions to install the extracted .img - but having some issues getting into fastboot mode in order to execute the commands. Running adb devices results in expected output, as does adb reboot recovery. However running adb reboot bootloader causes the device to reboot all the way back through to the lockscreen. I see some advice stating that to manually enter fastboot you reboot the device holding power+vol down, then pressing down to switch to the second option that isn't download mode. However that to me is the option to manually enter CWM Recovery, so now I'm confused. Running fastbooot reboot-bootloader cause
I don't want to brick my device, so I figured I'd ask for some advice here for getting into fastboot mode, and ask whether I can just flash the .zip inside CWM Recovery or if that is a very risky move?
Thanks in advance
Hey everyone, I'm brand new to this, and I was told before I start getting into ROMS that I need to run this software:
http://forum.xda-developers.com/showthread.php?t=1182871
So I followed each and every step, and my phone rebooted and it said "Unlocked" like it was supposed to. BUT, when it booted into the OS, it booted into the stock OS as if I had just bought it off the shelf. Additionally, I am seeing a little exclamation point and android character when I go to the Android Recovery option under fastboot (also installed via linked software)
What happened!?
Congratulations, you have just successfully unlocked the bootloader. Obviously you had higher hopes and were expecting bells and whistles, sorry to disappoint but that's it for this step. Next, flash a custom recovery via fastboot (I recommend the RomRacer's version of CWM), and then use that recovery to flash whatever ROM you choose. Instructions for all these steps are available in other threads. Good luck!
ravilov said:
Congratulations, you have just successfully unlocked the bootloader. Obviously you had higher hopes and were expecting bells and whistles, sorry to disappoint but that's it for this step. Next, flash a custom recovery via fastboot (I recommend the RomRacer's version of CWM), and then use that recovery to flash whatever ROM you choose. Instructions for all these steps are available in other threads. Good luck!
Click to expand...
Click to collapse
I thought when the phone rebooted after unlocking bootloader, it would boot back into the system I had before unlocking it? I flashed the "Tenfar recovery" that was in the automated script. However, when I flashboot into "Android Recovery," this is when I get to the exclamation point/ android character. Is this normal?
EDIT: I just reran the script to install recovery, and it seems to have worked the second time. I ran a backup and saved it on my external SD card, but is this backup of MY system, or of whatever its now booting into after being unlocked?
Ok guys, apparently I've somehow managed to screw this up. I swear I am following instructions completely!
I decided to try MIUI first, and so I made the backup, wiped all the data/cache/etc, and flashed the ROM. Upon reboot I discovered I couldnt get past the Dual Core screen. So, I rebooted into recovery and flash my backup, and have now found out that I cant get past the "Rethink Possible" screen.
Since at that point you haven't flashed anything else yet, the backup you made couldn't be anything else but your "normal" system.
No idea what (if anything) might've gone wrong, but here's something that you maybe didn't know - after flashing a new ROM, the following boot will always take MUCH longer than usual. After that the phone should boot at "normal" speed again. So have patience and give it time.
Also, not sure how come you're stuck at "rethink" screen. As far as I know that's the very end of the boot process, it is shown just before the launcher starts. Still, give it more time. If nothing happens after, say, 5 mins, try booting into recovery and wipe data and cache, then try booting normally again.
I think I may have found the problem. When I go to restore, it runs for a while, and then says "Error formatting /data"
What should I do?
Alright, im at a loss here. I've done everything I can think of. I've tried every restore setting possible, I've wiped everything MANY times, I've flashed a few diff ROMS to try to get ANYTHING to work.
I am utterly confused about why none of this is working. I've read so much info on the forums that my head is just swimming. I never thought this would be that hard.
At this point I'd just like to get ANYTHING working so that I have a usable phone tomorrow.
sounds like you're having lots of fun :laugh: try not to worry... we've all been there to varying degrees
If this was me I wouldn't go down the 'fastboot' method but just stick to accessing android recovery by the 'power off/on, hold volume down when powering on, and then selecting android recovery'
After this you should be into the phone's recovery mode with the menu in front of you? scroll down to 'wipe data/factory reset' and select (by pressing the power button) after this select 'wipe cache partition' and repeat the process.
Then go to 'install zip from sd card' and select this... if you have installed the ROM's correctly you should have a list at the bottom of the 'sd card' list? Select the rom you want and install by pressing power button ect.
Once this has been installed you then need to 'go back' to the main recovery page and then select 'reboot system'
Let us know if this helps... and good luck!
i would add wipe all (data & cache) again after installing!
I would try this:
Power down your phone, go to fastboot mode (Power + Vol-, then find Fastboot with Vol- and confirm with Vol+), connect to computer, then on the computer run these commands:
Code:
moto-fastboot erase -w
moto-fastboot reboot-bootloader
Then in the same menu as before, select Android recovery (and confirm with Vol+). When in recovery, try doing restore again.
If that doesn't work either, here's an alternative method to wipe /data from recovery using adb.
When in recovery, connect the phone to the computer and run this:
Code:
adb shell
That should place you in the phone's shell. Now in recovery go to Mounts and storage > Mount /data.
Then in the phone shell (on the computer) run this:
Code:
mount | grep /data
It should print something like:
Code:
[color=red]/dev/block/mmcblk0p[B]XX[/B][/color] on /data type ext3 (rw,nodev,noatime,nodiratime,errors=continue,data=ordered)
Note the first value printed. For me it's /dev/block/mmcblk0p16 but I'm not sure if that goes for all Atrixes out there, so better safe than sorry.
Now go back to recovery and select Mounts and storage > Unmount /data.
Now back to the computer - run this:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p[B]XX[/B]
Where XX is obviously what you got from the previous command.
When it's done (you get your prompt back), type exit and go back to recovery on the phone. Now you can try restoring your backup or flashing a ROM or whatever.
Solved
barry_ said:
sounds like you're having lots of fun :laugh: try not to worry... we've all been there to varying degrees
If this was me I wouldn't go down the 'fastboot' method but just stick to accessing android recovery by the 'power off/on, hold volume down when powering on, and then selecting android recovery'
After this you should be into the phone's recovery mode with the menu in front of you? scroll down to 'wipe data/factory reset' and select (by pressing the power button) after this select 'wipe cache partition' and repeat the process.
Then go to 'install zip from sd card' and select this... if you have installed the ROM's correctly you should have a list at the bottom of the 'sd card' list? Select the rom you want and install by pressing power button ect.
Once this has been installed you then need to 'go back' to the main recovery page and then select 'reboot system'
Let us know if this helps... and good luck!
Click to expand...
Click to collapse
This is EXACTLY the process I had been using. I just tried this again with MIUI, and again I got the screen that said MIUI was successfully installed from the sdcard. I rebooted, and now I've been stuck at the "Dual Core" unlocked screen.
gianluca.tomat said:
i would add wipe all (data & cache) again after installing!
Click to expand...
Click to collapse
No luck im afraid.
ravilov said:
I would try this:
Power down your phone, go to fastboot mode (Power + Vol-, then find Fastboot with Vol- and confirm with Vol+), connect to computer, then on the computer run these commands:
Code:
moto-fastboot erase -w
moto-fastboot reboot-bootloader
Then in the same menu as before, select Android recovery (and confirm with Vol+). When in recovery, try doing restore again.
Click to expand...
Click to collapse
How do I do this on the computer? What do I type it into?
wvcaudill2 said:
This is EXACTLY the process I had been using. I just tried this again with MIUI, and again I got the screen that said MIUI was successfully installed from the sdcard. I rebooted, and now I've been stuck at the "Dual Core" unlocked screen.
Click to expand...
Click to collapse
This is because the recovery you used is an outdated one.Install rom racer recovery, you can install it through fastboot http://forum.xda-developers.com/showthread.php?t=1204500
harishatrix said:
This is because the recovery you used is an outdated one.Install rom racer recovery, you can install it through fastboot http://forum.xda-developers.com/showthread.php?t=1204500
Click to expand...
Click to collapse
How do I enter these flashboot commands into the computer?
wvcaudill2 said:
How do I enter these flashboot commands into the computer?
Click to expand...
Click to collapse
As you don't know about fastboot I would suggest you to download automatic bootloader unlock from here http://forum.xda-developers.com/showthread.php?t=1182871, unzip it, you will find img file named " recovery-clockwork-4.0.1.4" replace it with romracer recovery you downloaded and rename the romracer recovery as " recovery-clockwork-4.0.1.4". Just to be safe even replace the "recovery-en-goapk-0630-1029" with rom racer recovery and rename it as "recovery-en-goapk-0630-1029". Open main and select option 6 and follow the on screen instructions.
harishatrix said:
As you don't know about fastboot I would suggest you to download automatic bootloader unlock from here http://forum.xda-developers.com/showthread.php?t=1182871, unzip it, you will find img file named " recovery-clockwork-4.0.1.4" replace it with romracer recovery you downloaded and rename the romracer recovery as " recovery-clockwork-4.0.1.4". Just to be safe even replace the "recovery-en-goapk-0630-1029" with rom racer recovery and rename it as "recovery-en-goapk-0630-1029". Open main and select option 6 and follow the on screen instructions.
Click to expand...
Click to collapse
Okay, so I did this and then went in and reflashed MIUI and it worked! Of course, now that I think about it, I should've created a new backup or something, but I guess its too late now.
On a side note, where can I find that google apps package?
wvcaudill2 said:
Okay, so I did this and then went in and reflashed MIUI and it worked! Of course, now that I think about it, I should've created a new backup or something, but I guess its too late now.
On a side note, where can I find that google apps package?
Click to expand...
Click to collapse
You will find the link for gapps from thread you downloaded the rom, I would suggest youto flash CWM touch recovery as it will make future flashing easy. Download it from here http://forum.xda-developers.com/showthread.php?t=1475444, and flash it the way you flashed the rom. Try out neutrino Rom if you are looking for fast and battery efficient rom
There are fruitcakes if you want to go back to stock rom.
harishatrix said:
You will find the link for gapps from thread you downloaded the rom, I would suggest youto flash CWM touch recovery as it will make future flashing easy. Download it from here http://forum.xda-developers.com/showthread.php?t=1475444, and flash it the way you flashed the rom. Try out neutrino Rom if you are looking for fast and battery efficient rom
There are fruitcakes if you want to go back to stock rom.
Click to expand...
Click to collapse
Could you link me to these "fruitcakes," and do I flash them like everything else?
wvcaudill2 said:
Could you link me to these "fruitcakes," and do I flash them like everything else?
Click to expand...
Click to collapse
Here you go http://forum.xda-developers.com/showthread.php?t=1163009 and yes you have to flash it like all other roms.
I've unlocked the bootloader to my Wileyfox Spark X using "fastboot flashing unlock" from my Ubuntu PC. I've flashed twrp recovery image (twrp-3.2.1-0-porridgek3.img
from https://dl.twrp.me/porridgek3/) having renamed it to twrp.img:
[email protected]:/home/john/Software/WileyfoxSparkX# fastboot flash recovery twrp.img
target reported max download size of 134217728 bytes
sending 'recovery' (13154 KB)...
OKAY [ 0.378s]
writing 'recovery'...
OKAY [ 0.347s]
finished. total time: 0.726s
But I can't get into SuperSU 2.82 (using SuperSU-v2.82-201705271822.zip) even though I've put it into the root directory of the internal SD card. There's no obvious option from the Android Recovery menu (i.e. Reboot system now, Reboot to bootloader, Apply update from ADB, Apply update from SD card,....). I've tried Apply update from SD Card and selected the SuperSU .zip file but it comes up with ""installation aborted" after "Update verification took 0.2 s (result 1)" with no other help. Any ideas?
I've tried TWRP 3.0.2-0. It gets into TWRP menu. I selected Install but "it seems /system cannot be mounted anymore and TWRP thinks no system is installed)". After letting it finish, Root Checker (not unsurprisingly) says that device is not rooted. BTW I've emailed TWRP Support (from their web page) asking if they have a working version.
johnaaronrose said:
I've tried TWRP 3.0.2-0. It gets into TWRP menu. I selected Install but "it seems /system cannot be mounted anymore and TWRP thinks no system is installed)". After letting it finish, Root Checker (not unsurprisingly) says that device is not rooted. BTW I've emailed TWRP Support (from their web page) asking if they have a working version.
Click to expand...
Click to collapse
Don't bug the TWRP developers for a specific version of TWRP which isn't even maintained by them.
Can you mount /system at all? Try pressing the "Mount" button in the main menu and let me know. You aren't supposed to install anything from the Android Recovery menu, you can only install OTA updates through that menu and its functionality is pretty much limited.
Where did you get that version of TWRP from? (I'd appreciate it if you linked me the thread)
AlwaysLivid said:
Don't bug the TWRP developers for a specific version of TWRP which isn't even maintained by them.
Can you mount /system at all? Try pressing the "Mount" button in the main menu and let me know. You aren't supposed to install anything from the Android Recovery menu, you can only install OTA updates through that menu and its functionality is pretty much limited.
Where did you get that version of TWRP from? (I'd appreciate it if you linked me the thread)
Click to expand...
Click to collapse
I assumed that the Wileyfox Spark X (i.e. porridgek3) version is maintained by the TWRP developers because the various versions come from:
https://dl.twrp.me/porridgek3/
Currently, I can't get into TWRP again. It's all hit & miss getting into TWRP:
1. If I do anything after flashing (e.g. booting as normal), I have to go into fastboot & flash TWRP again.
2. Once I have flashed TWRP (i.e. sill in fastboot mode), I can't leave fastboot mode. Also, the phone will not switch off unless I remove the battery and put it back in after approx 10 seconds.
3. Even then it often refuses to load TWRP i.e. it goes into the Android Boot menu. Could that be due to needing e.g. 70% battery charged?
At the moment the battery is 50% charged. So I'll fully charge it and post about the mount of /system using TWRP, assuming that I can get into TWRP.
BTW I did find a thread on https://android.stackexchange.com/questions/160130/how-do-i-install-systemless-supersu-in-samsung The interesting comment is #5. It says:
Sometimes the need for a systemless installation of SuperSU is not detected by the installation script, to force this to occur follow the following steps.
Start TWRP 3.0 or higher on the device
Go to Advanced - Terminal
In the terminal, enter echo SYSTEMLESS=true>>/data/.supersu
Press Enter
Exit to the TWRP main menu
Flash the current SuperSU as per normal
When flashing SuperSU, you should see in the TWRP recovery log screen mentions of system-less installation and patching of the boot image.
Is this the solution to rooting on the Spark X?
johnaaronrose said:
I assumed that the Wileyfox Spark X (i.e. porridgek3) version is maintained by the TWRP developers because the various versions come from:
https://dl.twrp.me/porridgek3/
Currently, I can't get into TWRP again. It's all hit & miss getting into TWRP:
1. If I do anything after flashing (e.g. booting as normal), I have to go into fastboot & flash TWRP again.
2. Once I have flashed TWRP (i.e. sill in fastboot mode), I can't leave fastboot mode. Also, the phone will not switch off unless I remove the battery and put it back in after approx 10 seconds.
3. Even then it often refuses to load TWRP i.e. it goes into the Android Boot menu. Could that be due to needing e.g. 70% battery charged?
At the moment the battery is 50% charged. So I'll fully charge it and post about the mount of /system using TWRP, assuming that I can get into TWRP.
BTW I did find a thread on https://android.stackexchange.com/questions/160130/how-do-i-install-systemless-supersu-in-samsung The interesting comment is #5. It says:
Sometimes the need for a systemless installation of SuperSU is not detected by the installation script, to force this to occur follow the following steps.
Start TWRP 3.0 or higher on the device
Go to Advanced - Terminal
In the terminal, enter echo SYSTEMLESS=true>>/data/.supersu
Press Enter
Exit to the TWRP main menu
Flash the current SuperSU as per normal
When flashing SuperSU, you should see in the TWRP recovery log screen mentions of system-less installation and patching of the boot image.
Is this the solution to rooting on the Spark X?
Click to expand...
Click to collapse
Yeah, that's normal. The battery percentage here doesn't really matter, but you could try to boot to TWRP using fastboot. You can also boot to TWRP by executing "fastboot boot recovery.img". You can also flash TWRP *through* TWRP.