Hi
I'm in the process of recovering a bricked Photon 4G. Not sure There's a chance to actually succeed.
I managed to gain root. But then accidentally used "Atrix2Bootstrap" to unlock the bootloader.
After restarting the phone got stuck on the dual core screen.
I tried entering cold boot, recovery mode for a factory reset and unlocking fastboot as described here :http://forum.xda-developers.com/showthread.php?t=1573727.
Then I tried recovery via rsd lite following this guide:
http://forum.xda-developers.com/showthread.php?t=1202666
But got the following error:
Flash failure: Phone[0000]: Error sending RAM download for bootloader.
Is there a way to recover the phone with fastboot? Or any other method?
thanks.
p.s
The phone had the most recent update installed : OTA 45.4.13.MB855
edit:
solved thanks to acvice's post and the battery trick which for unknown reasons was the only way to enter bootstrap recovery
(install bootstrap recovery, shutdown, remove battery for a minute, insert battery, plug to wall and boot normally).
You can not unlock, if you are on the latest OTA.
Follow this thread to unbrick your device, thats the inly way.
http://forum.xda-developers.com/showthread.php?t=1798145
peetr_ said:
This will recover from brick, when you are permanently locked on Photon after 2.3.5 OTA update.
Take USC_19 full sbf from 2.3.5 sv2 custom sbf thread, flash that, wipe data in recovery, root it, install bootstrap recovery.
After that, you can flash mof 2.3.5ish rom or my rom (locked).
Then install bootstrap recovery again, if it's not preinstalled there. And flash 254_13 modules. After that flash 2.3.5sv2 unbrick sbf with 254_13 boot, recovery and cdrom. If you have no radio service, flash 254_12 libmoto_ril.so.
Click to expand...
Click to collapse
Did someone say copypasta?!
I believe this will fix you.
Your input looks very promising.
I'll check it out.
Edit:
2.3.5_USC_19 sbf is still downloading. In the meanwhile I tried flashing the smaller "2.3.5_254_13 sv2 boot, recovery and cdrom image sbf"
and get the same error as before:
Failed flashing process. Failed flashing process. Phone[0000]: Error sending RAM download for bootloader. Device API Error: 0xE0030009 Command: ADDR (0xE0231009); Phone connected.
Is this a side effect from using the atrix2bootstrap app. Or maybe because i'm running win 7 64bit?
vrid said:
Your input looks very promising.
I'll check it out.
Edit:
2.3.5_USC_19 sbf is still downloading. In the meanwhile I tried flashing the smaller "2.3.5_254_13 sv2 boot, recovery and cdrom image sbf"
and get the same error as before:
Failed flashing process. Failed flashing process. Phone[0000]: Error sending RAM download for bootloader. Device API Error: 0xE0030009 Command: ADDR (0xE0231009); Phone connected.
Is this a side effect from using the atrix2bootstrap app. Or maybe because i'm running win 7 64bit?
Click to expand...
Click to collapse
You havta follow the instructions in order. Flash the sbf with rsdlite first =) Make sure you have the motorola 64bit windows drivers installed.
Acvice said:
You havta follow the instructions in order. Flash the sbf with rsdlite first =) Make sure you have the motorola 64bit windows drivers installed.
Click to expand...
Click to collapse
thanks, your were right, although the flash process got interrupted it was enough for the phone to boot up.
It now thinks it's an electrify.
I managed to root using photon-torpedo but the bootstrap recovery isn't working. It says "install success" but refuses to reboot into the bootstrap recovery mode. It just shuts down and when i manually boot it up it goes back to android.
any thoughts?
(small detail for others who are also stuck, I did the flash from a 32bit XP box. Not sure flashing from 7 64bit wouldn't work because i didn't try it)
vrid said:
thanks, your were right, although the flash process got interrupted it was enough for the phone to boot up.
It now thinks it's an electrify.
I managed to root using photon-torpedo but the bootstrap recovery isn't working. It says "install success" but refuses to reboot into the bootstrap recovery mode. It just shuts down and when i manually boot it up it goes back to android.
any thoughts?
(small detail for others who are also stuck, I did the flash from a 32bit XP box. Not sure flashing from 7 64bit wouldn't work because i didn't try it)
Click to expand...
Click to collapse
Making progress! It shouldnt boot directly to recovery. Youll havta do the hold vol down and power while booting up then scroll dow to android recovery using vol down and vol up to select.
And what do you mean the flash got interrupted?
vrid said:
thanks, your were right, although the flash process got interrupted it was enough for the phone to boot up.
It now thinks it's an electrify.
I managed to root using photon-torpedo but the bootstrap recovery isn't working. It says "install success" but refuses to reboot into the bootstrap recovery mode. It just shuts down and when i manually boot it up it goes back to android.
any thoughts?
(small detail for others who are also stuck, I did the flash from a 32bit XP box. Not sure flashing from 7 64bit wouldn't work because i didn't try it)
Click to expand...
Click to collapse
If you hav installed bootstrap & you press recovery mode, be sure phone is connected to wall charger.....
then only you would go in recovery mode....
Cooldevil1989 said:
If you hav installed bootstrap & you press recovery mode, be sure phone is connected to wall charger.....
then only you would go in recovery mode....
Click to expand...
Click to collapse
It was connected to the wall. I did boot into recovery manualy but found the standard recovery. not the installed bootstrap recovery.
When bootstrap recovery installed it stated "su binaries outdated" so i'm guessing that might be in indicator.
@ acvice. the error message :
"Failed flashing process. Interface BP: Error sending JUMP command Device API Error: 0xE003003F Address: 0x800000 Command: Jump (0xE053203F); phone connected
edit:
I updated the su binaries but still no bootstrap recovery. tried manualy entering recovery as well...
any alternate bootstrap recovery methods i could try?
First of all, tell me how u access recovery mode....???
Don't use power button to access recovery...
Sent from my MB855 using xda app-developers app
Cooldevil1989 said:
First of all, tell me how u access recovery mode....???
Don't use power button to access recovery...
Click to expand...
Click to collapse
well i boot up the phone by pressing the power and volume down buttons. Then scroll to recovery and press volume up.
How else should i enter recovery mode? after i install bootstrap and press recovery mode the phone simply shuts down without restarting by itself.
When u press recovery mode in boot strap recovery remember wall charger must be connected to phone... then only u will boot into recovery. ...
Sent from my MB855 using xda app-developers app
update:
The phone entered bootstrap recovery.
I pressed install. after the success message i simply returned to the home screen and let the battery die.
then i connected the phone to the wall and turned it on only pressing on the power button (no combinations).
then the bootstrap recovery screen finally showed.
so now i managed to flash MOF 2.3.5.ish v1.4.
I guess this is solved...
thank you for the replies and help.
Related
Following instructions here http://forum.xda-developers.com/showpost.php?p=20331623&postcount=6 to unlock/relock boot loader. Everything works fine until I flash the nopudding4u.sbf. After that I get the Failed to boot 4 message. Any help would be appreciated!
Photon4GUser said:
Following instructions here http://forum.xda-developers.com/showpost.php?p=20331623&postcount=6 to unlock/relock boot loader. Everything works fine until I flash the nopudding4u.sbf. After that I get the Failed to boot 4 message. Any help would be appreciated!
Click to expand...
Click to collapse
It says "Starting RSD Mode" after right? If you're trying to relock the bootloader, you should be able to flash any of the SBFs to get it locked again.
Correct - but this thread http://forum.xda-developers.com/showthread.php?t=1281528 suggests that you can relock, get back 4G and keep UbunTop & WebTop+. If I flash back an sbf such as 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-198_7-CM-release-keys-signed-Sprint-US.sbf the phone is relocked but the original WebTop is installed.
Photon4GUser said:
Correct - but this thread http://forum.xda-developers.com/showthread.php?t=1281528 suggests that you can relock, get back 4G and keep UbunTop & WebTop+. If I flash back an sbf such as 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-198_7-CM-release-keys-signed-Sprint-US.sbf the phone is relocked but the original WebTop is installed.
Click to expand...
Click to collapse
Webtop+/Ubuntop with 4G
Root-Unlock-Relock.zip
Flash 198_7 SBF then root, unlock and install CWM Recovery.
Flash WebTop+ 1.2
Factory reset phone Menu/Settings/Privacy/Factory Data Reset DO NOT SKIP THIS STEP
Reboot phone into fastboot mode: VOL down/Power. Use VOL down to scroll though options til you see "fastboot" then VOL up to enable. and connect phone to computer
Open command prompt in the moto-fastboot folder and type the following using the <enter> key after each command:
moto-fastboot devices
moto-fastboot erase recovery
moto-fastboot flash recovery stock_recovery.smg
moto-fastboot reboot
Disconnect phone from computer
Start RSD Lite on your computer
Reboot phone into RSD mode: VOL down/Power. Use VOL down to scroll though options til you see "RSD" then VOL up to enable.
Connect phone to computer.
Flash nopudding4u.sbf.
Close RSD Lite and disconnect phone.
Reboot phone
Thanks for the response. This is exactly what I was following - got this error after step 10 (tried 3 different times).
I'm digging through this to see where the issue is. I'll keep you updated.
Found the issue and fixed it.
Thanks! That worked! Appreciate the support!
This thread (and the link to the explanation) was very helpful. Lokifish Marz, you might want to make a note in the WT+ post (http://forum.xda-developers.com/showpost.php?p=17956277&postcount=2) for people to be sure to reflash the full 198_7 or 198_6 SBF and specifically not try to relock without full SBF flash (which is shown in the guide.htm in the Root-Unlock-Relock zip). Just to draw attention that the full SBF Flash is required, since I (probably like OP) tried the quickest/simplest route to relocking first.
Hi,
I was trying to install Cyanogenmod on my phone using the guide on the cyanogenmod wiki (I can't post the link, but it's the first google result for Motorola Atrix 4G: Full Update Guide)
I did everything in the guide, up to the point where I was supposed to flash the ROM onto my phone using RSD, but then it failed and gave me a "Error switching phone to BP Pass through mode". I unplugged it from the computer, took out the battery put it back in, and now it's giving me the
"Failed to boot 0x1000
No OS detected, going to RSD mode
in 5 seconds
...
..."
Menu. When plug my computer back in, and try to flash the same ROM using RSD Lite again, it says "Failed Flashing Process: Unable to retrieve interface handle". How do I fix this? I've never unlocked or rooted my phone or anything before. It was completely stock before I tried to do this.
Also, when trying to use fastboot and typing in fastboot oem unlock, it's just stuck on <waiting for device>
You tried to rsd a flashable rom on a locked bootloader phone. Your first error. You will need to rsd back to stock first. Then you need to root the phone. Then You need to follow the steps in the guide here http://forum.xda-developers.com/showthread.php?t=1202883 or here http://forum.xda-developers.com/showthread.php?t=1182871 (the second one I used recently). Once you've done that stuff THEN you can flash cm thru recovery. Hope you didn't hard brick.
pre4speed said:
You tried to rsd a flashable rom on a locked bootloader phone. Your first error. You will need to rsd back to stock first. Then you need to root the phone. Then You need to follow the steps in the guide here http://forum.xda-developers.com/showthread.php?t=1202883 or here http://forum.xda-developers.com/showthread.php?t=1182871 (the second one I used recently). Once you've done that stuff THEN you can flash cm thru recovery. Hope you didn't hard brick.
Click to expand...
Click to collapse
Thanks for your help, but could you be more specific on how to do all of that? As you can tell, I'm (quite obviously) a noob at this.
Also: I downloaded a file called 1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012 , which is supposed to be the stock ROM. But when I run RSD, it gives me the error "Failed Flashing Process: Unable to retrieve interface handle (0x7027)
EDIT:: Your second link worked! Thank you very much!
Don't worry about it, it is common. All you need is the small unlock RSD file for your device found in post # 1136261 and the attempted flash that fails in the step that you described. Then you need to move on to the next step in the process. You need to get the phone into fastboot though, by holding the volume down key during the boot up / or if you get that crazy menu with options 0 though 9, use the volume up and down to select fastboot. Then on the PC continue with the process:
fastboot oem unlock
Then when that is successful, flash recovery.img or whatever recovery you have downloaded:
fastboot flash recovery recovery.img
Sent from my MB860 using Tapatalk 2
MCDong said:
Thanks for your help, but could you be more specific on how to do all of that? As you can tell, I'm (quite obviously) a noob at this.
Also: I downloaded a file called 1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012 , which is supposed to be the stock ROM. But when I run RSD, it gives me the error "Failed Flashing Process: Unable to retrieve interface handle (0x7027)
EDIT:: Your second link worked! Thank you very much!
Click to expand...
Click to collapse
You're welcome!
Hello,
I 'm new to the android community and i'm so glad to be among you. So i rooted my HTC Desire X (with ICS) a couple of days ago using CWM recovery and now I want to install this DEODEXED stock ROM: http://forum.xda-developers.com/showthread.php?p=40682127
(Note: I have CID:T-MOB101 and HBOOT 1.24.0000).
While rooting the phone i installed CWM recovery while the guide on the link demands to install TWRP. How can i install TWRP over CWM? Because while doing the steps of the guide i got stuck in the 3rd step(Command Prompt says:sending "recovery" but the process never finishes)...
Forgive me if i have forgotten any info of my phone, just let me know!
Thanks in advance,
Tassos
Download this tool http://forum.xda-developers.com/showthread.php?t=1943822
Its much easier.
Important! make a nandroid backup first before flash anything,
ειναι σημαντικο να εχεις ενα!!
Tried with the way above, didn't worked...
I tried this and it didnt worked, i also tried manually through terminal with no luck. As i said above the process gets stuck when the terminal says "sending recovery" and the bar on the screen of my phone doesn't fill. I 've been reading that there are some other users of HTC DX that have the same problem with me, that is they can't flash TWRP and finally they install CWM. Has this something to do with the details of my phone(CID, hboot, etc.)?
So can anyone help me on how to flash TWRP on my phone with CWM on it.?
tassos_chry said:
How can i install TWRP over CWM?
Click to expand...
Click to collapse
Try Clearing the Dalvik Cache
Download this toolkit ,extract it on desktop
replace its recovery.img with this RECOVERY
boot into bootloader
Connect to PC
run 'Install Recovery.img.bat'
AND U"RE DONE :laugh:
if this does not work then try factory format
AND REMEMBER MAKE AN NAND :good: BEFORE DOING THIS
Thanks
Ok thanks, i'll try these methods and post feedback.
Thanks again
Update:
First method didn't work...
Just tried factory reset!
Update 2:
I factory resetted the phone through CWM and went to repeat the process. Still NO luck...
tassos_chry said:
Ok thanks, i'll try these methods and post feedback.
Thanks again
Update:
First method didn't work...
Just tried factory reset!
Update 2:
I factory resetted the phone through CWM and went to repeat the process. Still NO luck...
Click to expand...
Click to collapse
1. Start your PC
2. Go in folder containing fastboot.exe and related binaries.
3. Download the recovery.img for (ICS or JB) as required.
4. Type this command in cmd.exe
fastboot.exe flash recovery recovery.img
5. Press power button so that phone goes from fasboot to hboot mode. Then press VOLDOWN and then POWER to boot into recovery.
Its a simple enough process, just try to be calm and do it one step at a time.
Regards
Yasir
Sorry for not posting this earlier, but i just saw that when i boot into hboot the following message comes up:
"SD Checking
Loading PM66DIAG.zip
No Image
Loading PM66DIAG.nbh
No Image
Loading PM66IMG.zip
No Image
Loading PM66IMG.nbh
No Image or Wrong Image"
Then it disappears immediately and the normal screen of hboot comes up...
Maybe this has something to do, with me not being able to flash TWRP...
Any help?
tassos_chry said:
Sorry for not posting this earlier, but i just saw that when i boot into hboot the following message comes up:
"SD Checking
Loading PM66DIAG.zip
No Image
Loading PM66DIAG.nbh
No Image
Loading PM66IMG.zip
No Image
Loading PM66IMG.nbh
No Image or Wrong Image"
Then it disappears immediately and the normal screen of hboot comes up...
Maybe this has something to do, with me not being able to flash TWRP...
Any help?
Click to expand...
Click to collapse
I said to you thru PM... check whether you are at the correct fastboot usb screen. This SD checking and blablabla is hboot screen, fastboot flash won't work on hboot screen, only on fastboot/bootloader screen.
After this SD checking and blablabla screen, press power once to go to bootloader/fastbboot screen
ckpv5 said:
I said to you thru PM... check whether you are at the correct fastboot usb screen. This SD checking and blablabla is hboot screen, fastboot flash won't work on hboot screen, only on fastboot/bootloader screen.
After this SD checking and blablabla screen, press power once to go to bootloader/fastbboot screen
Click to expand...
Click to collapse
All the times I've tried to flash a recovery i 'm on the fastboot/bootloader screen, which says Fastboot USB. I tried with neXus PRIME's way too but it didn't work out. I think i'm not doing anything wrong and don't know why it doesn't work...
Check/change your cable and also change the usb port (use usb2.0 instead of usb3.0) or try on other PC
BTW.. you also can use CWM to flash ROM... the only reason to use TWRP is it has a reboot option in recovery where you can select reboot to bootloader. So using CWM, you must manually put your device to bootloader after installing ROM.
But I suggest, you stick with your current ROM. That JB ROM is only for people who want to test how the JB ROM is. Most of them revert back to ICS
ckpv5 said:
Check/change your cable and also change the usb port (use usb2.0 instead of usb3.0) or try on other PC
BTW.. you also can use CWM to flash ROM... the only reason to use TWRP is it has a reboot option in recovery where you can select reboot to bootloader. So using CWM, you must manually put your device to bootloader after installing ROM.
But I suggest, you stick with your current ROM. That JB ROM is only for people who want to test how the JB ROM is. Most of them revert back to ICS
Click to expand...
Click to collapse
FML. It was the USB port that caused the mess(I was using USB 3). Just flashed TWRP using USB 2
Thank you man. I was so dissapointed, thinking that something is wrong with my phone!!
Thank you very much!:laugh:
Update:Any info when the official update for JB from HTC comes out for all of us who don't have it yet?
I am new to cell phone mods. My goal was to gain some experience by rooting and replacing the os image on my Atrix 4G. I use it for my alarm clock which uses an application that won't run on newer version of android than v2.x.x. I successfully rooted and installed super use. I then installed Titanium Backup and did a full backup to sdcard. I installed Rom Manager, chose ClockworkMod Recovery and then the correct image, and told it to flash the recovery partition. Rebooted. Got an error with the android logo and a circle with a triangle. Went back to all the how to's and attempted to install unlockable_bootloader. It now comes up to rsd, seems to fail, then goes into fastboot. Fastboot devices sees it and I can reboot from fastboot but it goes back to the same place. HELP.
Forget about any and all automatic methods, including ROM manager and similar. Good old-fashioned manual methods work best.
Try this guide. http://forum.xda-developers.com/showthread.php?t=2262869
ravilov said:
Forget about any and all automatic methods, including ROM manager and similar. Good old-fashioned manual methods work best.
Click to expand...
Click to collapse
I think I have read all the posts and how to's on manually flashing. Temporarily recovered but persued my goal of learning something. Only thing it can do now is fastboot when I hold the volume key UP while restarting. Used to be down but that's gone. RSD protocol is no more. Says "Failed to boot 1" when restarting. Something I flashed apparently relocked the boot loader and who knows what else I've screwed up. Fastboot -w indicates it cas erase the cache and userdata partitions. Surely there is still hope for this as I can still access fastboot. Can you give a little help please?
Phatdaddy said:
I think I have read all the posts and how to's on manually flashing. Temporarily recovered but persued my goal of learning something. Only thing it can do now is fastboot when I hold the volume key UP while restarting. Used to be down but that's gone. RSD protocol is no more. Says "Failed to boot 1" when restarting. Something I flashed apparently relocked the boot loader and who knows what else I've screwed up. Fastboot -w indicates it cas erase the cache and userdata partitions. Surely there is still hope for this as I can still access fastboot. Can you give a little help please?
Click to expand...
Click to collapse
Ỳou need to download the image of the recovery partition and flash it using fastboot flash recovery recovery.img
flash recovery failed
andresrivas said:
Ỳou need to download the image of the recovery partition and flash it using fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I previously found a thread that described that process and tried it. Fastboot reported it failed flashing recovery.
That usually happens if the BL is not unlocked (properly).
Phatdaddy said:
I think I have read all the posts and how to's on manually flashing. Temporarily recovered but persued my goal of learning something. Only thing it can do now is fastboot when I hold the volume key UP while restarting. Used to be down but that's gone. RSD protocol is no more. Says "Failed to boot 1" when restarting. Something I flashed apparently relocked the boot loader and who knows what else I've screwed up. Fastboot -w indicates it cas erase the cache and userdata partitions. Surely there is still hope for this as I can still access fastboot. Can you give a little help please?
Click to expand...
Click to collapse
reflash the pudding sbf to unlock the bl, then go ahead and flash recovery as advised. if I remember correctly, when it says failed to boot 1, its automatically in rsd, which means just hook it up and let rsd lite do its job then fastboot for recovery
flash boot failed
palmbeach05 said:
reflash the pudding sbf to unlock the bl, th
en go ahead and flash recovery as advised. if I remember correctly, when it says failed to boot 1, its automatically in rsd, which means just hook it up and let rsd lite do its job then fastboot for recovery
Click to expand...
Click to collapse
Installed pudding successfully with RSD Lite. Attempted to flash recovery with "fastboot flash recovery image_name". Reports "sending recovery" and then "writing recovery". When I reboot, it still has has the stock recovery utility.Otherwise, I'm back to stock 2.3.6 except that it reports unlocked upon rebooting. Am I not flashing the correct thing? Thanks for the pointers.
Phatdaddy said:
Installed pudding successfully with RSD Lite. Attempted to flash recovery with "fastboot flash recovery image_name". Reports "sending recovery" and then "writing recovery". When I reboot, it still has has the stock recovery utility.Otherwise, I'm back to stock 2.3.6 except that it reports unlocked upon rebooting. Am I not flashing the correct thing? Thanks for the pointers.
Click to expand...
Click to collapse
hmm, sounds like you're on the 145 build of 2.3.6. Check to see what your phone says in about phone. its going to give you a system version ending in 141 or 145.
palmbeach05 said:
hmm, sounds like you're on the 145 build of 2.3.6. Check to see what your phone says in about phone. its going to give you a system version ending in 141 or 145.
Click to expand...
Click to collapse
This one says "4.5.141". Before undertaking to hack this piece, it was 4.5.145. I have flashed preinstall and boot and attempted to flash recovery. I don't know where it stores the build number. Could it be reporting .141 while really .145 ? I am confident the .145 is correct because we have two phones purchased the same day from same vendor and the other reports .145. I also remember it as .145 but my memory is pretty faulty.
Phatdaddy said:
This one says "4.5.141". Before undertaking to hack this piece, it was 4.5.145. I have flashed preinstall and boot and attempted to flash recovery. I don't know where it stores the build number. Could it be reporting .141 while really .145 ? I am confident the .145 is correct because we have two phones purchased the same day from same vendor and the other reports .145. I also remember it as .145 but my memory is pretty faulty.
Click to expand...
Click to collapse
ok. I think the file we need to look for in order to fix this is in system/etc. its called install-recovery.sh and that file forces stock recovery to be installed. delete that file and try flashing the custom recovery.
palmbeach05 said:
ok. I think the file we need to look for in order to fix this is in system/etc. its called install-recovery.sh and that file forces stock recovery to be installed. delete that file and try flashing the custom recovery.
Click to expand...
Click to collapse
ls of /system/etc/install-recovery.sh says the file does not exist.
When I bricked my atrix i used the xatrix tool to unbrick it. works really well and once unbricked was fully unlocked so was easy to flash new roms
xatrix (dot) webs (dot) com
once on there website click to download tab to get the downloads
This tool will remove everything from phone root, unlock and install cwm. What you do after that is upto you. sometimes its easier to start over then figure out what went wrong when installing a mod.
My problem is now this, I'm recovered, rooted, and unlocked. If I flash recovery with fastboot, it says I am successful but when I reboot the original recovery image still exists.
And thats the part that confuses me. It says 141, but the recovery issue is acting like its a 145. I'm stumped, but i do believe there is an install-recovery.sh script or something thats preventing this thing from sticking after flashing. I'm really baffled by this b/c i ran 141 for the longest time, i did all my rooting, unlocking, and recovery flashing on 141, and got no issues. I could advise that you download and flash the ICS leak (the true leak, not the ROMs we have available) via fastboot and see if that changes the situation, but i don't want to advise you to do something and then a bigger mess appears.
Sent from my MB886 using xda app-developers app
Phatdaddy said:
My problem is now this, I'm recovered, rooted, and unlocked. If I flash recovery with fastboot, it says I am successful but when I reboot the original recovery image still exists.
Click to expand...
Click to collapse
sounds like you had 145 installed and flashed 141 over it without doing a wipe first. i would use cwm recovery and do a factory reset wipe all data and flash the rom you want to run.
overboard1978 said:
sounds like you had 145 installed and flashed 141 over it without doing a wipe first. i would use cwm recovery and do a factory reset wipe all data and flash the rom you want to run.
Click to expand...
Click to collapse
he can't get cwm installed. it may say it gets flashed correctly, but he cannot get cwm to show up and be usable.
as a work around, via fastboot, run the commands:
fastboot erase data
fastboot erase cache
that would cover what factory reset does.
palmbeach05 said:
he can't get cwm installed. it may say it gets flashed correctly, but he cannot get cwm to show up and be usable.
as a work around, via fastboot, run the commands:
fastboot erase data
fastboot erase cache
that would cover what factory reset does.
Click to expand...
Click to collapse
That should do it. If for some reason it doesnt the xatrix tool will wipe everything off the phone and start it over with 141 unlocked bootloader, with cwm. Only automated tool i found that will unbrick phone with rsd lite. Make sure phone is fully charged before starting xatrix tool as it wipes battery fast and if it dies you will need to start over.
Erase cashe was successful, erase data failed. Found reference to additional file to delete but it did not exist either. If I conttinue, I will repost. Thanks for everyone's effort trying to get this working.
I wanted to upgrade my Nabi with the latest OTA. I had TWRP 2.2.2.1. I used it to revert to an old backup. After the restore, I tried to apply the OTA updates. After it rebooted and started the install I got an "!" Android logo.
I power cycled and I was able to boot back in. I noticed I still had the Play Store app (which will not work, error about connecting to services) and suspect the "stockunrooted" restore I used may not have been completely "stock". I did lose root and TWRP though.
I tried to reinstall TWRP again, but it appears that Fastboot no longer works since the restore. The tablet just hangs on the Nabi logo indefinitely. When I press Vol - & + with PWR, and select Recovery Mode, I just get another "!" Android logo (is this stock recovery?).
ADB works, it sees the tablet and I'm able to push, access shell etc.
I used motochopper to root the Nabi again. I tried installing flash_image to manually flash a new TWRP recovery.img, but running the command I get an error about "error scanning partitions".
I'm not sure what else I can do to get Fastboot working or a recovery system installed again. OTA upgrade will not apply, and I'm stuck on 1.9.37 at this point.
Does anyone have a suggestion how I can get Fastboot fixed and the Nabi back to "normal" / upgradeable.
Thanks for your help
kaijan said:
I wanted to upgrade my Nabi with the latest OTA. I had TWRP 2.2.2.1. I used it to revert to an old backup. After the restore, I tried to apply the OTA updates. After it rebooted and started the install I got an "!" Android logo.
Click to expand...
Click to collapse
What software rev did you get to when doing the OTA's?
I power cycled and I was able to boot back in. I noticed I still had the Play Store app (which will not work, error about connecting to services) and suspect the "stockunrooted" restore I used may not have been completely "stock". I did lose root and TWRP though.
Click to expand...
Click to collapse
That is usually a sign that various Google services are removed from the system partition. So in that case it is returned to stock, but there is still information of the Play install on the data partition.
I tried to reinstall TWRP again, but it appears that Fastboot no longer works since the restore. The tablet just hangs on the Nabi logo indefinitely. When I press Vol - & + with PWR, and select Recovery Mode, I just get another "!" Android logo (is this stock recovery?).
ADB works, it sees the tablet and I'm able to push, access shell etc.
I used motochopper to root the Nabi again. I tried installing flash_image to manually flash a new TWRP recovery.img, but running the command I get an error about "error scanning partitions".
I'm not sure what else I can do to get Fastboot working or a recovery system installed again. OTA upgrade will not apply, and I'm stuck on 1.9.37 at this point.
Click to expand...
Click to collapse
Usually when it hangs at the Nabi logo it means you don't have the USB cable plugged in or that the fastboot driver is not installed.(Check device manager and see if fastboot driver is installed/no exclimation point). If that's not the issue then it's the bootloader which I have only seen one person have that issue. Depending on which OTA's you have ran there was an update to a Jellybean bootloader so it's possible. That can be fixed with nvflash or placing the bootloader blob in the staging partition.
Also you can always get recovery back without fastboot in Android by dd'ing the recovery over.
For example if the recovery image is on the internal SD
dd if=/data/media/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
aicjofs said:
What software rev did you get to when doing the OTA's?
That is usually a sign that various Google services are removed from the system partition. So in that case it is returned to stock, but there is still information of the Play install on the data partition.
Usually when it hangs at the Nabi logo it means you don't have the USB cable plugged in or that the fastboot driver is not installed.(Check device manager and see if fastboot driver is installed/no exclimation point). If that's not the issue then it's the bootloader which I have only seen one person have that issue. Depending on which OTA's you have ran there was an update to a Jellybean bootloader so it's possible. That can be fixed with nvflash or placing the bootloader blob in the staging partition.
Also you can always get recovery back without fastboot in Android by dd'ing the recovery over.
For example if the recovery image is on the internal SD
dd if=/data/media/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
Click to expand...
Click to collapse
OTA is trying to install 2.1.27
You were correct about the fastboot driver issue. I was using Windows 8.1 and it it wasn't working properly. I switched to Ubuntu and now have no problems.
I was able to flash TWRP 2.3.3 and tried another restore to stock. Did OTA again, but still get the "!" Android shortly after it reboots and starts installing. I can't seem to get rid of gapps either. Play Store is still installed. I've tried wiping /data/media, cache's etc and it still remains.
I'm not sure why the OTA upgrade keeps failing. Do you think it's due to the gapps still being on the device?
Any other ideas on how I can get the OTAs to work?
Update:
I booted up stock recovery and tried the update from cache
Verifying current system...
assert failed: apply_patch_check("/system/app/Gallery2.apk", "4cadedee1defcdc28afc99ea968ebb1e631e7b9", "ee310bfc0d0ad2fe11356b97f8cb6e754aa43f2b")
E: Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
kaijan said:
OTA is trying to install 2.1.27
You were correct about the fastboot driver issue. I was using Windows 8.1 and it it wasn't working properly. I switched to Ubuntu and now have no problems.
I was able to flash TWRP 2.3.3 and tried another restore to stock. Did OTA again, but still get the "!" Android shortly after it reboots and starts installing. I can't seem to get rid of gapps either. Play Store is still installed. I've tried wiping /data/media, cache's etc and it still remains.
I'm not sure why the OTA upgrade keeps failing. Do you think it's due to the gapps still being on the device?
Any other ideas on how I can get the OTAs to work?
Update:
I booted up stock recovery and tried the update from cache
Click to expand...
Click to collapse
Hmm that is it weird. It does look like gapps is still installed .As gapps removes gallery2.apk and why it's failing, I don't understand if it's stock how that is happening. Use these updates yet? http://forum.xda-developers.com/wiki/Fuhu_nabi_2
This thread died out....I hate to bump it back to the top...But I have a NABI2-NV7A that I rooted along time ago....and i booted it up and was gonna do some upgrades and everything went kaboom!!
I have TWRP 2.2.2.1 installed.
I can get into TWRP but not fast-boot mode
I'm on a laptop with windows 10 installed...I don't think it's driver related....as i can send commands via adb while TWRP is up....and the NABI responds to those commands
But i never get past the logo screen....and I'm not sure what to to do with NVflash.
I'm experienced...but rooted this thing and installed GAPPS like 2 years ago and the kids dug this thing up and the play store wouldn't work any longer....i read about the OTA....so i was trying to go back to stock and get those OTA's.
Any suggestions or advice?? Anyone...hello....bueller....bueller
hotspace said:
This thread died out....I hate to bump it back to the top...But I have a NABI2-NV7A that I rooted along time ago....and i booted it up and was gonna do some upgrades and everything went kaboom!!
I have TWRP 2.2.2.1 installed.
I can get into TWRP but not fast-boot mode
I'm on a laptop with windows 10 installed...I don't think it's driver related....as i can send commands via adb while TWRP is up....and the NABI responds to those commands
But i never get past the logo screen....and I'm not sure what to to do with NVflash.
I'm experienced...but rooted this thing and installed GAPPS like 2 years ago and the kids dug this thing up and the play store wouldn't work any longer....i read about the OTA....so i was trying to go back to stock and get those OTA's.
Any suggestions or advice?? Anyone...hello....bueller....bueller
Click to expand...
Click to collapse
Have you tried using "adb reboot-bootloader"
There are some things to try before breaking out nvflash. The easiest would be to flash the boot loader and a new TWRP in one recovery session.
Boot twrp2.2.21, Install KK boot loader zip and then install TWRP KK287 zip
Then restore the 3.0.13 ROM
Files and directions here
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
aicjofs said:
Have you tried using "adb reboot-bootloader"
There are some things to try before breaking out nvflash. The easiest would be to flash the boot loader and a new TWRP in one recovery session.
Boot twrp2.2.21, Install KK boot loader zip and then install TWRP KK287 zip
Then restore the 3.0.13 ROM
Files and directions here
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
Click to expand...
Click to collapse
I did try ADB REBOOT-BOOTLOADER all that happens is the NABI2 restarts and sits at the logo screen.
I'm able to push via ADB, so I will download the suggested files and take your advice. I'll report back. And, thanks for the reply.
Update...
I was able to push all of the needed files and I verified I pushed them completely by using "adb push -p xxxxxx /sdcard"
I then rebooted back into TWRP
I flashed KK3013bootloader.zip, then flashed twrp-recovery-NV7AUS-287.zip
Rebooted and I can't get back into TWRP. And, now I can't establish a connection for adb commands.
Any advice? tips...pointers? Could this truly be my first bricked device??
hotspace said:
Update...
I was able to push all of the needed files and I verified I pushed them completely by using "adb push -p xxxxxx /sdcard"
I then rebooted back into TWRP
I flashed KK3013bootloader.zip, then flashed twrp-recovery-NV7AUS-287.zip
Rebooted and I can't get back into TWRP. And, now I can't establish a connection for adb commands.
Any advice? tips...pointers? Could this truly be my first bricked device??
Click to expand...
Click to collapse
Nah Nabi2 is practically impossible to brick.
So do you get the command list in the top left when you press the vol and power buttons? i.e the selection continue, fastboot, recovery kernel, forced recovery? or when you select recovery kernel it just doesn't boot TWRP?
I wont type a lot of stuff until I get you answer but if we need to go the nvflash route this is some good reading. You will need to get in to APX mode, install the driver and issue some commands.
Read this post and next few pages after it
http://forum.xda-developers.com/showpost.php?p=46579190&postcount=1687
General idea of commands
http://forum.xda-developers.com/showpost.php?p=48683262&postcount=124
Might be some work, but we should be able to get the device back, I'll let you know which is the best way after I see your reply.
Yup, no boot options. And, I can't get back into TWRP. I hold power button to shut it down. Then vol+ power and typically I'd get the boot options, but nothing, just the logo. Then hold power button to shut down. Continue...repeat...
I appreciate you sticking in for the long haul on this.
Sent from my SM-N920P using Tapatalk
hotspace said:
Yup, no boot options. And, I can't get back into TWRP. I hold power button to shut it down. Then vol+ power and typically I'd get the boot options, but nothing, just the logo. Then hold power button to shut down. Continue...repeat...
I appreciate you sticking in for the long haul on this.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Damn. It IS going to be a long haul, but you will know the tablet well when its done. I don't have the tablet to test anymore, so I have to work from memory(and that's been a long time)
Well the bad news is this is going to require opening the tablet. See this post http://forum.xda-developers.com/showpost.php?p=46694284&postcount=1701
You are going to have to short those pins to get it in to APX mode and use nvflash
-You will need the APX driver as well.
-The nvflash package
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
I will type more later.
aicjofs said:
Damn. It IS going to be a long haul, but you will know the tablet well when its done. I don't have the tablet to test anymore, so I have to work from memory(and that's been a long time)
Well the bad news is this is going to require opening the tablet. See this post http://forum.xda-developers.com/showpost.php?p=46694284&postcount=1701
You are going to have to short those pins to get it in to APX mode and use nvflash
-You will need the APX driver as well.
-The nvflash package
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
I will type more later.
Click to expand...
Click to collapse
Sweet! Looking forward to this.
Sent from my SM-N920P using Tapatalk
hotspace said:
Sweet! Looking forward to this.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Get the nvflash package from the Nabi General Info thread I linked above
Unzip in to a directory of your choosing and open a command prompt in that folder
The Nabi will be broken open and connected by USB to computer
So once you get those pins shorted and press the power button the screen should come on and be completely black(you can tell the backlight is on though)
Check in device manager for a new device(it will be auto detected or you will have to manually install APX driver)
Once the driver is installed you can issue nvflash commands
nvflash --bl bootloader.bin --download 4 bootloader.bin
Before pressing enter for the below command get ready to press and hold the vol+ key.
nvflash --resume --go
Right on. I'll dig into this in the morning
Sent from my SM-N920P using Tapatalk
@aicjofs, I still haven't begun breaking the Nabi down. I'm working from home today and should be able to squeeze the disassemble in sometime today.
I scanned through the comments you've left since finding out I wasn't able to get to the boot menu...I'll post back once I get it torn apart.