Related
I formated my sd card from recovery-windows and i got a bootloop when i rebooted it.
No more access to recovery-windows, i took off my sd card, bootloop again, i had to go to recovery with red triangle, pull off battery, disconnect from usb and reboot to make it work.
Factory is reset but no more network even with proper settings, and i can't access the recovery windows without having bootloop all over again. I got a mysterious IMEI SV number now too.
Strange things is the drivers are mad in hboot and recovery now , i got something like this.
I don't understand what went wrong, can someone point me in the right direction to make it work?
is your phone rooted?
shara6 said:
is your phone rooted?
Click to expand...
Click to collapse
Yes, with blay0 0.7 currently on it.
So the network came back after one complete day without it. Don't ask me why.
But i have other major issues:
-SD Card slot not recognize, tested with different SD cards, same result.
-Bootloop when i boot my phone, only way to get around it is to plug it in usb, don't ask me why too.
-Weird Drivers still nuts with HTC DIAG, Qualcomm CDMA Technology not recognize.
I didn't know a simple SD card format from recovery can cause so much trouble :'(
Undoubtly the native drivers from Hboot disappeared, and without sd card nor recovery from PC, i don't know how to bring them back.
Can someone help me please, i don't want to lose it :'(
Okay it's a classic USB Brick sorry for the inconvenience.
Turned my phone off and back on a couple of days ago and now the phone boot loops after showing the telstra logo.
I have Hboot and fastboot access but no recovery. (does the same thing, just boot loops), even though I had clockworkmod installed. It's as if everything just wiped itself.
My hboot is version 0.80.0008 and it says S-ON.
What could I do from here to revive my phone? Would a gold card be the only way?
I have created some other posts but none had been replied to, any help would be greatly appreciated.
Maxcima.
i've had one bootloop before, which was solved by removing sd card and booting up then replacing, hope it helps.
ephbee said:
i've had one bootloop before, which was solved by removing sd card and booting up then replacing, hope it helps.
Click to expand...
Click to collapse
Thanks for the suggestion but I've already tried booting without the SD card in with no success. It's quite frustrating because I was only playing music before I turned it off.
Any other suggestions? Anyone?
which rom are you using?
my h-boot is 0.80.0004 s on.
was there anything new loaded on phone prior to your bootloop problem?
i had another issue after loading some new tunes on sd card, even though they were fine on pc, they made my phone schitz out, kept on rebooting and made sd card read only, i know its a longshot but i'm trying to think of anything i can
I'm using SUnAaBh v1.1 which is quite ironic because it was renowned to be one of the most reliable and stable roms out there haha.
I did get fruit ninja but it had been a while since I reset it so I don't know for sure what it could be since I've put various things on, but none that I could think of that would potentially force a boot loop.
I do really appreciate your help. It provides some hope until I can get my hands on a gold card
Is there any other way that you know of to flash it while it is in the current state?
have you tried rooting using unrevoked again and installing clockworkmod?
What mode would I have to be in for unrevoked to recognise my phone?
As I cannot boot into the phone, USB debugging is a no go. Does unrevoked recognise a device in fastboot or something similar?
Thanks.
Boot into Clockmod Recovery and then try to clear cache & DALVIK cache. Then boot again and wait some Minutes.
Maxcima said:
Turned my phone off and back on a couple of days ago and now the phone boot loops after showing the telstra logo.
I have Hboot and fastboot access but no recovery. (does the same thing, just boot loops), even though I had clockworkmod installed. It's as if everything just wiped itself.
My hboot is version 0.80.0008 and it says S-ON.
What could I do from here to revive my phone? Would a gold card be the only way?
I have created some other posts but none had been replied to, any help would be greatly appreciated.
Maxcima.
Click to expand...
Click to collapse
Sent from my HTC Wildfire using XDA App
Deep-Knight said:
Boot into Clockmod Recovery and then try to clear cache & DALVIK cache. Then boot again and wait some Minutes.
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
Hi Deep-Knight. That would have been my first option but as I stated, for some reason selecting recovery from HBOOT just makes the device loop boot after the telstra logo again, it doesn't boot into clockworkmod recovery anymore.
I don't understand why.
Thanks
Maxcima said:
What mode would I have to be in for unrevoked to recognise my phone?
As I cannot boot into the phone, USB debugging is a no go. Does unrevoked recognise a device in fastboot or something similar?
Thanks.
Click to expand...
Click to collapse
was your phone already with usb debugging enabled before this bootloop? if it was already enabled, unrevoked will work fine.
(i always keep it enabled)
Hmm, originally when I used unrevoked I would have had it enabled (obviously) but since then I've flashed other roms using clockworkmod. So everytime you flash a new rom, it gets rid of USB debugging unless you enable it again correct?
Therefore I don't think USB debugging is enabled on mine. Ahh, it's so annoying.
I have it on HBOOT and plugged into my pc but Unrevoked isn't picking it up, I assume it's because I don't have USB debugging enabled, or am I wrong?
Thanks guys, really appreciate it!
it shouldn't change usb debugging, all the roms i have flashed its still there after being turned on once. check your messages too, sent you some info on telstra
Oh okay, I still have no luck with unrevoked though. Tried it on a different PC with the HBOOT modified drivers. Just stuck on "Waiting for device..."
ADB commands also do NOT work, so I am lead to believe that usb debugging is NOT enabled?
Please correct me if I'm wrong.
Thanks.
EDIT: NEVER MIND, I got it working! I found a recovery zip (PC49IMG.zip) and renamed the cyanogenmod as update.zip, put them both on my SD card and booted into recovery!
Clockwork stated there wasnt enough room on E: (whatever drive that is) so I flashed all data and installed cyanogenmod.
Thanks heaps everyone, means a lot to me
PS - I dont know why clockwork mod decided to boot this time but it did. Maybe because it had to room, it couldnt boot? I don't know, I'm not that experienced with these things.
good to hear mate, now go and get some credit from telstra
A little background:
I first installed CWM on my Nook Colour 2 years ago. A year later (for whatever reason), it reverted back to stock. I had no problem with this and continued using it. Then, roughly 4 months later, it suddenly entered a factory reset mode (after being turned on), during which I let it do its thing, and now I cannot seem to start it using any of the bootable SD's including the one found here:
http://forum.xda-developers.com/showthread.php?p=25354258#post25354258
Some specs that may be required:
I am using Linux Mint 14 to flash the SD using:
Code:
sudo dd if=CWM-5.5.04-bootable_SD.img of=/dev/mmcblk0
where /dev/mmcblk0 is pointing to the SD card. I then insert the SD card into the device and turn it on and/or plug it into the USB cable. Nothing happens. When I plug it into my Windows machine, it detects the device as "OMAP3630", referencing the processor but not the actual device. Would anyone have any expertise on this matter? Thank you very much.
Code:
of=/dev/mmcblk0
That bit looks wrong. You want to burn it to the microSD card. In Linux, you can list devices by "sudo blkid" and they usually use the format "/dev/sdXY". Do you have a microSD card reader handy? If you do, use that. If you don't, order one off Amazon, they cost $6 with free shipping and handling.
You can't easily brick these tablets unless you do something really crazy, like messing up the partition table or deleting /boot.
I'm certain that this is it. The only two drives available via gparted are sda1 (my laptop's hard drive) and mmcblk0 (only found when the MicroSD adapter is inserted).
sagirfahmid3 said:
Code:
of=/dev/mmcblk0
That bit looks wrong. You want to burn it to the microSD card. In Linux, you can list devices by "sudo blkid" and they usually use the format "/dev/sdXY". Do you have a microSD card reader handy? If you do, use that. If you don't, order one off Amazon, they cost $6 with free shipping and handling.
You can't easily brick these tablets unless you do something really crazy, like messing up the partition table or deleting /boot.
Click to expand...
Click to collapse
In gparted, set the boot flags of the microSD to lba and boot (checkmark them). I had to do that to install CWM to my Nook Tablet, maybe it could work for the NC as well.
What kind of microSD adapter are you using?
sagirfahmid3 said:
In gparted, set the boot flags of the microSD to lba and boot (checkmark them). I had to do that to install CWM to my Nook Tablet, maybe it could work for the NC as well.
What kind of microSD adapter are you using?
Click to expand...
Click to collapse
Yep, I have been doing this, to no avail. I'm using an ADATA microSD adapter.
http://nookdevs.com/NookColor/RestoreToStock
Sounds like you didn't flash an unlocked bootloader before installing cwm, so you're still stuck on the stock boot loader I think. Maybe you used the rom manager method after rooting the stock ROM. The method above should reset your nook back to stock, assuming you're on the stock boot loader.
sagirfahmid3 said:
Sounds like you didn't flash an unlocked bootloader before installing cwm, so you're still stuck on the stock boot loader I think. Maybe you used the rom manager method after rooting the stock ROM. The method above should reset your nook back to stock, assuming you're on the stock boot loader.
Click to expand...
Click to collapse
Hi sagirfahmid,
Thanks for the help. Unfortunately, neither of the tips can help at this point. The Nook Colour will not turn on and it isn't being detected by either lsusb nor adb. Any other tips? Thanks.
x711Li said:
Hi sagirfahmid,
Thanks for the help. Unfortunately, neither of the tips can help at this point. The Nook Colour will not turn on and it isn't being detected by either lsusb nor adb. Any other tips? Thanks.
Click to expand...
Click to collapse
Try plugging in a powered USB cable, like your charger, and try booting it up. It should at least get to the "read forever" screen or something. From there you could do the 8 failed boots method.
sagirfahmid3 said:
Try plugging in a powered USB cable, like your charger, and try booting it up. It should at least get to the "read forever" screen or something. From there you could do the 8 failed boots method.
Click to expand...
Click to collapse
I have been doing this. The screen does not turn on at all or boot up.
Any other tips? Or is this the end of my Nook Colour?
x711Li said:
Any other tips? Or is this the end of my Nook Colour?
Click to expand...
Click to collapse
Try the recovery section from this user's thread. He made a complete Nook Color guide to anything and everything you might possibly do (including bricks): http://forum.xda-developers.com/showthread.php?p=25354258#post25354258
Hi guys. I had a 32gb G2 and i was able to root it, upgrade it to 4.4 and use it without a hitch.
Today i got another one (16gb version) and flashed a kitkat rom i had around without stopping to check if it was 16 or 32gb (i forgot they had this difference). Well, now i got phone that i cannot use (im stuck at the SIM card PIN). What happens is that the screen is erratic. i click 2 and it registers 7...i click 5 and it selects simultaneously 123 and so on. basically i cannot pass this screen to enable all the good stuff.
Is there any way i can solve this?
I have a LG G802.
mechlord said:
Hi guys. I had a 32gb G2 and i was able to root it, upgrade it to 4.4 and use it without a hitch.
Today i got another one (16gb version) and flashed a kitkat rom i had around without stopping to check if it was 16 or 32gb (i forgot they had this difference). Well, now i got phone that i cannot use (im stuck at the SIM card PIN). What happens is that the screen is erratic. i click 2 and it registers 7...i click 5 and it selects simultaneously 123 and so on. basically i cannot pass this screen to enable all the good stuff.
Is there any way i can solve this?
I have a LG G802.
Click to expand...
Click to collapse
Boot without SIM card, connect to USB and transfer correct ROM. Boot into recovery, flash proper ROM. If you can't boot without SIM card you can probably use adb push to just push the ROM onto the sdcard and then reboot to recovery + flash.
Agret said:
Boot without SIM card, connect to USB and transfer correct ROM. Boot into recovery, flash proper ROM. If you can't boot without SIM card you can probably use adb push to just push the ROM onto the sdcard and then reboot to recovery + flash.
Click to expand...
Click to collapse
Ok. will implement & report
My problems just keep getting worse.
Since i wanted to go full stock i ended up downloading a kdz file a nd followed the tutorial on http://unbrick.itcse.com/unbrick-soft-bricked-lg-g2/
well...that didnt work. the process initiated and somewhere along the way the app stopped, and the only thing i could undestand was a "EMERGENCY something". After like 1hr with nothing happening, i unplugged the phone and got some corrupted partitions.
I then turned to the tutorial on http://forum.xda-developers.com/showthread.php?t=2582142 ...but damn! i cant reboot properly. now all the phone does is boot up to the lg logo and nothing else happens. windows doesnt detect it, linux doesnt detect it and adb doesnot detect it. am actually crying now....IS THERE ANYTHING I CAN DO TO SOLVE THIS?....im kinda desperate here. This is a brand new phone!
mechlord said:
My problems just keep getting worse.
Since i wanted to go full stock i ended up downloading a kdz file a nd followed the tutorial on http://unbrick.itcse.com/unbrick-soft-bricked-lg-g2/
well...that didnt work. the process initiated and somewhere along the way the app stopped, and the only thing i could undestand was a "EMERGENCY something". After like 1hr with nothing happening, i unplugged the phone and got some corrupted partitions.
I then turned to the tutorial on http://forum.xda-developers.com/showthread.php?t=2582142 ...but damn! i cant reboot properly. now all the phone does is boot up to the lg logo and nothing else happens. windows doesnt detect it, linux doesnt detect it and adb doesnot detect it. am actually crying now....IS THERE ANYTHING I CAN DO TO SOLVE THIS?....im kinda desperate here. This is a brand new phone!
Click to expand...
Click to collapse
maybe i could try to mess with the partitions and this time try to install some twrp that actually works? the one in the last tutorial doesnt seem to work on my 16gb model.
I was trying to root my phone using the information/program on http://forum.xda-developers.com/ver...b6-of1-n900v-note-3-verizon-oneclick-t3333569 . The program started to run and seemed to be working but it never finished or I was an idiot who didn't give it enough time. Either way, I now have a phone that I can only get to the bootloader screen but it isn't unlocked so I can't put a new ROM on it and the factory reset doesn't get me back in. Is there any way to unlock from here or do I need to seek out and download the stock Verizon ROM and install it again via the SD card?
mwolf00 said:
I was trying to root my phone using the information/program on http://forum.xda-developers.com/ver...b6-of1-n900v-note-3-verizon-oneclick-t3333569 . The program started to run and seemed to be working but it never finished or I was an idiot who didn't give it enough time. Either way, I now have a phone that I can only get to the bootloader screen but it isn't unlocked so I can't put a new ROM on it and the factory reset doesn't get me back in. Is there any way to unlock from here or do I need to seek out and download the stock Verizon ROM and install it again via the SD card?
Click to expand...
Click to collapse
After you get your phone back to 5.0 stock, run the one click root again on win 10 using the stock cable if you have it, then install SuperSU. Go to thread Official bootloader unlock for Verizon note 3 by ryanbg. This will completely unlock bootloader and you can install TWRP. But read the warning thread about using the new version.
I'm new at this but it worked for me
Good luck, some of those threads have info on getting you back to normal
Thank you for your reply. Unfortunately, right now I'm not sure if I'll even be able to get back to 5.0. The original USB cable is a thought as I'm not able to get the PC to see the phone. My only access is SD card so far.
mwolf00 said:
Thank you for your reply. Unfortunately, right now I'm not sure if I'll even be able to get back to 5.0. The original USB cable is a thought as I'm not able to get the PC to see the phone. My only access is SD card so far.
Click to expand...
Click to collapse
If you:
- pull battery, wait 10 sec, insert battery. (USB *not* plugged in)
- startup w/ Vol-Down+Home+Power
- select "Cancel" when warning splash screen displays
what happens? Does it hang for a while before it goes back to the Odin Download screen?
I'm not aware of any method to install from the SD card.
(Maybe w/Mobile Odin but that doesn't apply here).
99% of the time if there is a connectivity issue between the phone & the PC, the issue is on the Windows side if things.
bftb0 said:
If you:
- pull battery, wait 10 sec, insert battery. (USB *not* plugged in)
- startup w/ Vol-Down+Home+Power
- select "Cancel" when warning splash screen displays
what happens? Does it hang for a while before it goes back to the Odin Download screen?
I'm not aware of any method to install from the SD card.
(Maybe w/Mobile Odin but that doesn't apply here).
99% of the time if there is a connectivity issue between the phone & the PC, the issue is on the Windows side if things.
Click to expand...
Click to collapse
When I go through the steps you suggest, after I select the cancel action, the phone restarts and enters the boot loader with very little delay. The whole process takes about 10 seconds.
I've downloaded the stock ROM. Is there a way to install it from SD card? Can I use Odin on it to create a file the phone can boot from? It seems there should be something I can do...
Also - As for the connectivity issue being on the windows side, before this whole process, I had no issues connecting to the phone from Windows so I do not believe it is on that side...
mwolf00 said:
When I go through the steps you suggest, after I select the cancel action, the phone restarts and enters the boot loader with very little delay. The whole process takes about 10 seconds.
I've downloaded the stock ROM. Is there a way to install it from SD card? Can I use Odin on it to create a file the phone can boot from? It seems there should be something I can do...
Also - As for the connectivity issue being on the windows side, before this whole process, I had no issues connecting to the phone from Windows so I do not believe it is on that side...
Click to expand...
Click to collapse
'
Whew - I was able to get the stock ROM back on the phone. There was a pending update on my PC which might or might not have been part of the issue. After the restart, I was able to us Odin to push it back on. Now to root the thing again...