Related
Hi all,
I had rooted my nook tablet using snowball mod about a week ago and I loaded CWM on to the emmc using indirect's one-click recovery flash app. It was all working fine.
I wanted to return to stock and so put the 1.4.0 zip on my sdcard and rebooted. But it went straight to CWM. So I remembered i had to restore the stock recovery and rebooted and flashed stock recovery. only this time, I used the updated version of the one-click app (the updated version of 26th Jan) and hit reboot to recovery. This caused my NT to be in a boot loop ever since.
I have tried the 8 failed reboot method to initiate a factory reset but it didn't work. I also tried using the Nook Recovery Fix but i can't get to install the drivers since if I connect the NT to my computer, it keeps rebooting over and over again and I can't get to show for longer than 2 secs in device manager to install the drivers for Windows. (I was using it on Ubuntu till now).
My NT just turns on, the black screen n logo shows (The "With adobe reader" screen) however it doesn't go any farther than that. It just shuts down. The white nook screen does not even show. It's like it's going through multiple failed reboots without me holding down any buttons. Any help from you guys is greatly appreciated. Thanks.
You have to make a bootable SD with CWM on it so that the computer can actually catch the Nook long enough to do anything. Also, I'm pretty sure the B&N drivers restrict what you can do, but I'm not really sure what's gonna happen if you connect for the first time in CWM. I say use the Nook and Zergy method for the drivers (the first part, runmefirst.bat)
After that, try the Nook Recovery. It should work. I'm not positive on this, but from what I've read, that's what you do.
CWM SD:
http://forum.xda-developers.com/showthread.php?t=1446987
Really though, no promises. Good luck. Lemme know how it turns out.
Data Injures said:
You have to make a bootable SD with CWM on it so that the computer can actually catch the Nook long enough to do anything. Also, I'm pretty sure the B&N drivers restrict what you can do, but I'm not really sure what's gonna happen if you connect for the first time in CWM. I say use the Nook and Zergy method for the drivers (the first part, runmefirst.bat)
After that, try the Nook Recovery. It should work. I'm not positive on this, but from what I've read, that's what you do.
CWM SD:
http://forum.xda-developers.com/showthread.php?t=1446987
Really though, no promises. Good luck. Lemme know how it turns out.
Click to expand...
Click to collapse
Thanks a lot for your suggestion! I just spent a half hour on the phone with B&N customer service and they agreed to ship out a replacement device. The rep said it was a hardware failure that was causing it to act like that. I was a bit surprised at that. I'm not sure she knew what she was talking about. Anyway I had bought mine off craigslist. And now I'm getting a new device so I guess I can't complain. But I'll try later tonight to restore this one using the bootable CWM you linked to. Thanks again.
Follow Up
Just thought of posting a follow up. The bootable CWM method worked. I was able to fix the recovery. Most certainly not a HW problem like the tech claimed. It's working fine now.
I'm glad to hear that! Now if I have the same problem in the feature I can just follow my own advice. Lol
Sent from my DROIDX using XDA App
So I have basically the same problem. My girlfreinds nook was rooted but the OTA update stopped the root from being effective. I tried the sd card revert to 1.4.0 and I hade the problem with the "n" butting not working. When i tried the 8x reset the nook went into an endless boot loop where I see the back screen and the next white screen flashes for like 2 seconds and then reboots. I tried to make the CWM SD card but it still just reboots. My question is that since i never had the CWM mod installed am I pretty much hosed or am I doing something wrong?
What are you using to make the CWM SD card? I strongly recommend using GParted either from a Linux live image or there is a GParted live image you could use. When it works correctly, the bootable SD card that should stop the boot loop.
But why did the boot loop problem occur in the first place ?
sailerph said:
But why did the boot loop problem occur in the first place ?
Click to expand...
Click to collapse
From what I know of, if you install stock recovery and hit the reboot to recovery button, it initiates the stock recovery which then causes the error. Though I don't know the reason behind nor what's causing the problem, just relaying what I have read around the forums.
From what I understand when you flash CWM it's recovery replaces the stock recovery so when you try to install the stock recovery, which you should not do, it is trying to pull from something that's no longer there. I learned this lesson the hard way.
Denmmurray said:
From what I understand when you flash CWM it's recovery replaces the stock recovery so when you try to install the stock recovery, which you should not do, it is trying to pull from something that's no longer there. I learned this lesson the hard way.
Click to expand...
Click to collapse
Hm I actually unrooted my nook a couple of times to play with it. I reinstalled the stock recovery from the app on multiple occasions, but instead of clicking reboot to recovery, I ran the one click unroot and never ran into any trouble.
Hey All, hope this is the right area. I got my Prime and love it, but being an old
computer geek I wanted a better ROM. I let it update to .21 and regretted it of coarse.So I used the stock Asus unlocking tool, then Wolf's ultimate flash and downgrade(worked, took it back to .15) ViperBoy's newly updated PrimeTool 4.6 to root and installed TWRP 2.1. Everything seemed to be fine and I was ready for Android Open Kang
Project - Build 35. Yes it was awhile ago, AOKP looks great and I was drooling to get it in, but recovery didn't work. I have tried to flash different CWM's in, nothing seems to change my problem, I go into recovery and my Android guy is working for just few seconds, then keels over with the dreaded red exclamation mark sign, Dead. Yes my Asus still works with all it's bloatware and plods along but I really want to fix this and am just about desperate to try anything.
My computer has ADB access, and I have a novice's novice level of skills, can anyone,
anywhere help?
06-25-12
Just went through the rooting thing again. My device IS rooted, but NOTHING will get me in the recovery, now have also tried GooManager and ROM toolbox to attempt to install CWM over existing one(?) >sigh< Does anyone think using ADB to push another CWM would be for helpful then dangerous? Help?
I am a relative noob at flashing roms and rooting phones, but last night I ran into an issue. My phone was having all sorts of problems so I was going to put it back to factory, then start from scratch. I then decided to just flash a different rom. here is what happened.
I deleted SuperSU - this was done as part of the process to unroot and put back to factory, after this step I decided to flash a different rom
Put new ROM on phones internal memory as well as SD card
Wipe data
wipe cache and delvic cache
install new rom
Black screen
In an attempt to unbrick I relocked my bootloader.
Now, my phone can power on (Give white screen and HTC logo), then go black, and I can access Recovery mode. That is all.
I have plugged the phone to my computer and tried running the RUU, but the RUU will not recognize the phone.
I am not sure what to do to unbrick my phone and get it working again. Any and all help would be most appreciated!
Sorry I can't be more eloquent with my words, but I'm at work. I will be responding throughout the day, though.
thanks again so much to anyone that can help!
Try running it straight from bootloader
I loaded into Bootloader, selected Fastboot(USB), ran the .exe and it still won't recognize the phone. However, I did get recovery unlocked again. So I can get into recovery mode, flash all the ROMs I want, mount and unmount, yet still everytime I flash a new ROM it still boots to a black screen. Am I doing this right?
Try a Rom with kernel installer
Thanks! Since I am still a little new could you tell me how I would spot a ROM with kernel installer or could you point me to any one that could work? From then, it's the same process as flashing any other ROM? Do I need to do something with the kernel?
Meanbean and stock with goodies are the 2 that I'm certain of. Meanbean needs to be flashed twice the first time
Thanks so much for your help, I will post my results soon!
Failed
Here's what it says. Sorry for the blurry picture. I followed directions closely.
What version of recovery are you using? You may need to update it. Assuming you have a pc, try mounting the internal memory to pc through twrp. Windows will automatically tell you to format if its damaged
2.1 Updating now
omg it finally worked! Updated TWRP using fastboot and flashed MeanBean. Thank you so much!!!
Sorry I'm a noob at all of this. Successfully rooted my phone today thanks to Honsoon2000's excellent tutorial and toolkit. Then I went to install Android Revolution, which appeared to go successfully and then after I flashed the kernel the phone wouldn't load and just hangs at the quietly brilliant screen. I followed Honsoon's tutorial to the T (or so I thought) and everything went perfectly until right at the end when I flashed the kernel. I can make it back to the bootloader screen though it says "failed to load usb master mode". I can still make it into fastboot and recovery mode...tried recovery, and the process seemed to go sucessfully, but the phone still wouldn't load after...tried reinstalling ARHD-- it's still on the sd card and the install procedure still goes off without a hitch, but the phone still won't load. I've searched around and tried everything I can, to no avail. Any help would be muchly appreciated, and I apologize in advance for being a noob wasting people's time.
Edit: For example, when I follow the steps outlined in the FAQ it asks me to enter the command 'fastboot flash boot boot.img' , but when I do it says 'error: cannot load boot.img'.
Edit 2: So I put my boot.img file from Android Revolution into the data directory of the rooting toolkit and was able to complete the above flashboot command. I was also able to install the ROM off my SD card...however the phone still hangs on the Quietly Brilliant screen...I can't even power the phone down...whenever I try it just reboots...frustrating...really hoping someone can help me...cheers.
Before you begin, make sure that the drivers for the One X+ are installed.
Place the boot image being used on the computer's hard drive.
Boot in to recovery and flash the ROM.
When that is done, boot in to bootloader and connect the phone to the PC via a USB cable.
If the phone isn't in fastboot mode already, use the volume keys to highlight the word "fastboot", then press the power button.
Now, there should be text at the bootloader screen that says "Fastboot USB".
Finally, use the toolkit or command line and flash the kernel with the fastboot command.
This should successfully flash the ROM and the kernel. Make sure you full wipe before flashing a new ROM. If you can't seem to get the new ROM booting, the final choice is to relock the bootloader and run a RUU.
Which phone version you do own? International or AT&T / TELUS?
Did you flashed the correspondant boot.img? Did you cleared the cache? ( fastboot erase cache)
I'm trying to run an RUU but it keeps saying the battery isn't charged enough to flash anything...and this after it's been plugged in all day. Oh dear I think my phone might be done...really sucks :/
Also, it won't let me power the phone down-- every time i try it shuts the phone off briefly and then opens back up to the bootloader screen.
Fixed thanks to sarcasticphoenix. Cheers.
OK so I've tried 3 times to flash a new ROM onto my phone (Android Revolution twice and Eleganzia once) using Honsoon's toolkit...I've followed every instruction to the T as far as I can tell and all 3 times the process has gone perfectly right until the end when I flash the kernel...after that when I reboot the phone it just hangs at the Quietly Brilliant screen. I know how to relock the bootloader, flash the custom rom and get my phone back...but I really want to know what I'm doing wrong so I can install a custom ROM. I know I'm using the right ROM for my phone and am wondering what gives. Being driven crazy here...any ideas what's going wrong here would be helpful. BTW on the last attempt right after I finished and the phone hung I went into the boot loader and followed the instructions in the FAQ for fixing a bootloop...still nothing.
Edit: Solved my problem-- I managed to successfully load eleganzia...the only thing i did differently the last time was flash the kernel BEFORE installing the ROM off the SD card.
jrockwell said:
OK so I've tried 3 times to flash a new ROM onto my phone (Android Revolution twice and Eleganzia once) using Honsoon's toolkit...I've followed every instruction to the T as far as I can tell and all 3 times the process has gone perfectly right until the end when I flash the kernel...after that when I reboot the phone it just hangs at the Quietly Brilliant screen. I know how to relock the bootloader, flash the custom rom and get my phone back...but I really want to know what I'm doing wrong so I can install a custom ROM. I know I'm using the right ROM for my phone and am wondering what gives. Being driven crazy here...any ideas what's going wrong here would be helpful. BTW on the last attempt right after I finished and the phone hung I went into the boot loader and followed the instructions in the FAQ for fixing a bootloop...still nothing.
Edit: Solved my problem-- I managed to successfully load eleganzia...the only thing i did differently the last time was flash the kernel BEFORE installing the ROM off the SD card.
Click to expand...
Click to collapse
That's usually what I do first, flash the kernel and then install the zip via recovery
Sent from my HTC One X+ using xda premium
Which kernel are you referring too? Actually there is one or two kernels available but only for the International version, not the AT&T/TELUS which you seem to have.
I strongly suspect that your boot looping was because you didn't flash the boot.img file correctly or not at all. And you don't seem to install the good ROM version for your phone.
Elegancia has two ROM versions one for International and one for AT&T/TELUS users.
ARHD is for International users.
Please read Q12 of the FAQ.
Lucky Thirteen said:
ARHD is for International users.
Click to expand...
Click to collapse
Lol...yeah I don`t know how I missed that. I ended up getting elegancia successfully flashed and loaded so all is well. In retrospect this was a good experience because there`s nothing like having to get yourself unforked from a bad situation to gain an understanding of what`s going on. Cheers.
I have a couple questions and since I`m not allowed to post yet in the elegancia thread I'll try in this thread first:
1) An elegancia question: Is there a way (widget) to toggle data roaming on and off in this ROM?
2) Is there a way to tweak settings (transparent pull down, selection of launcher etc.) without wiping and reflashing the ROM?
3) What are people's favorite launcher for that ROM? I tried Atom but it was just a guess because I hadn't heard of any of them. I like it so far but am curious about the others.
Hi Guys,
i have a Sony Tablet S (first version, not Xperia) with 4.0.3 r5a (prerooted with AiO and old hidden.img) and it gets stuck on every second reboot, that means:
- Tablet is powered off
- Power on Tablet
- Tablet stuck on Sony logo (Logo refresh one time as you can see on the screen)
- Hold Power for 10 seconds to power down
- Tablet is powered off
- Power on Tablet
- Tablet boots normally
- Reboot Tablet from adb shell or app or just reboot manually (power off/power on)
- Tablet stuck on Sony Logo
- Power off 10 seconds
- Power on
- Tablet boots normally
........ and so on
What i have tried:
- Downgrade to 4.0.3 r1
- Connect via adb while stuck (not possible, adb does not recognize the device in this state)
- Wipe data (through recovery mode)
- Tried to find some log files which gives information (failed badly, logcat only produces output when tablet is already booted, no other logfile found)
Any ideas what could be the reason or what i should check?
Btw, the tab works perfect once it has booted up.
Keep on rockin'
Sony tablets have 2 boot partitions, one of yours is corrupt so the tablet boots to the other one. I think Condi's flasher can fix it, because it flashes both
Sent from my Nexus 4
lopezk38 said:
Sony tablets have 2 boot partitions, one of yours is corrupt so the tablet boots to the other one. I think Condi's flasher can fix it, because it flashes both
Sent from my Nexus 4
Click to expand...
Click to collapse
This is true, or since you have old recover you can use condi's double flash. If you use flasher please install the new recovery as well so it doesn't mess anything up.
I just reflashed 4.0.3 r5a with the actual AiO but so far the problem persists. Flashing went through flawlessly except the stuck on sony logo on the reboots and also the wipe after flash went through with no problems. Device is rooted and working, but still stuck on every second reboot.
Any other ideas?
Keep on rockin'
EDIT: I also tested it now with Flasher 3.0 (not AiO but also from condi) where i chose option 1 4.0.3 r5a wifi+3g and also flashed old recovery (option 2). I had no problems in the update process but the problem is still there.
i got same problem at 4.0
flash stock rom(root-able ver) then root it,the system is ok.
i guess aio tool have some bugs with none us regsions(my is china)
check your regaion.zip,file content,version and permition
Use his flasher tool, not the AiO
@robin
What exactly should i check on region.zip, anything special to look out for?
@lopezk38
As you might have read i also tried with the flasher tool, it wrote both partitions (current system and second system) but the problem persists.
Any other ideas how to fix this?
Keep on rockin'
Still nobody with an idea?
Just flashed custom_prerooted_doubleFLASH_R5A_nbx03_016-ota-121116077.zip from condi's thread @ http://forum.xda-developers.com/showthread.php?t=2020911 but still no luck, always stuck on second boot.
Although i had at least a little bit success with flashing 3.2.1 via AiO, after flashing it and getting stuck on reboot i wiped data in recovery mode and was able to boot at least once into 3.2.1, but after reboot i got stuck again and on second reboot it booted back to 4.0.3
At least that tells me that it is possible to boot from the partition, but something is still wrong.
I really appreciate all the help and the work from you guys.
On another note, i'm pretty firm with shell commands (long time linux user), anything i could try to check via adb shell?
Keep on rockin'
Corrupted for sure on the second boot partition, if double flashing does not help then something is really wrong with the second partition.
Sent from my Nexus 4 using xda app-developers app
andyabc said:
Corrupted for sure on the second boot partition, if double flashing does not help then something is really wrong with the second partition.
Click to expand...
Click to collapse
Leaves the question if there is a way to repair it, maybe by copying an image from the working partition with dd to the bad partition. I don' want to give up yet
DudemeisterAT said:
Leaves the question if there is a way to repair it, maybe by copying an image from the working partition with dd to the bad partition. I don' want to give up yet
Click to expand...
Click to collapse
Exactly same issue here since i rooted the device with last AIO 6.4 tool. Still searching for a solution too.
In the meantime i tried two more things to fix this problem.
First i copied the working partition to the not working partition with dd
dd if=/dev/mmcblk0p3 of=/dev/mmcblk0p2
The writing of the partition went through with no problems but it did not help at all. In my last effort to get system0 working again i tried flashing the OTA update (knowing that i will loose adb shell in recovery), but to my surprise after finishing the update successfully i was stuck with the same problem and a working adb shell. It seems OTA was flashed to system0 but is still not able to boot from it
I am running out of ideas and thinking about buying a new tablet (definitlely NOT a Sony Device anymore). Hopefully someone has another idea.
DudemeisterAT said:
In the meantime i tried two more things to fix this problem.
First i copied the working partition to the not working partition with dd
dd if=/dev/mmcblk0p3 of=/dev/mmcblk0p2
The writing of the partition went through with no problems but it did not help at all. In my last effort to get system0 working again i tried flashing the OTA update (knowing that i will loose adb shell in recovery), but to my surprise after finishing the update successfully i was stuck with the same problem and a working adb shell. It seems OTA was flashed to system0 but is still not able to boot from it
I am running out of ideas and thinking about buying a new tablet (definitlely NOT a Sony Device anymore). Hopefully someone has another idea.
Click to expand...
Click to collapse
I have the same problem, have you found a solution?
Sadly i was not able to fix it, i even tried to let the battery run out completely (was my last hope) but no change at all. I am thinking of sending it back again to sony for repair, cause now I am absolutely out of ideas, i think i tried everything possible.
Keep on rockin'
Sent from my Sony Tablet S using xda app-developers app
Any updates on this problem... BUMP
Sent from my Galaxy Nexus using Tapatalk 4
Sadly no, anyway i use my sgs4 more than the sony, much better Hardware just smaller screen. If there is a tab with the same or better specs (like sgs 4) i will buy a new one and give the sony to my brother. Farewell sony, i have enough of your crap.
Sent from my GT-I9505 using xda app-developers app
I have the same problem ! Any help would be greatly appreciated !
Did you try the things written in this thread?
Sent from my GT-I9505 using xda app-developers app
I don't know if there are still people interested in this but i finally got my tablet working again normally and booting up everytime.
Today i powered on the tablet after loading it fully and realised that there was no wifi anymore, i couldnt even enable the wifi adapter itself. After some other issues, including loosing root, i tried to reflash my backup. I went to recovery and selected the zip to flash which resulted in the "error in base sku" message. I tried different rom files which i had saved (custom signed, officialy signed) and none of them seemed to work. Rooting the device also did not work anymore, even if i tried manually executing all the commands, mostly i just got shut down by permission denied.
Anyway, after failing to try and flash the rom named signed-nbx03_016-ota-121116095.zip i luckily got the idea of renaming it to update.zip and put it in the root of the external sd card. I went back to recovery mode and selected the update.zip, flashing started and went through completely. The tablet rebooted and finished installing the rom and i ended up on the standard ics screen. I then took condis AiO and went to root the tablet and after the tablet rebooted it surprisingly booted again normally and after a quick check with super su i knew it was rooted. I did a couple of reboots with and without cable/ac adapter attached and now i am sure, it boots up every single time.
It looks like that the filename update.zip might tell the tablet to flash differently than with another name, at least i like to hope so. Maybe it helps someone out there with the Tab S.
Funny sidenote, two weeks ago i bought a SM-T805
Have fun