Database Develop

Root Loop?

Hi all,
I downloaded the modaco update-nexusone-FRF50-signed.zip, and flashed my stock 2.1 (out of the box) nexus one rom, it worked well for about 9 hours, i plugged it into my car charger and when i took it off, it froze, and the touch screen disabled. Now im trying to reflash the rom and keep getting stuck at E: Can't mount /dev/block/mmcblk0p1, then E: Can't mount SD card
Any ideas on how i can get this working again?
Thanks

reinsert your sdcard, I have issues where the sdcard doesn't sit properly. This is assuming your using a2sd

i have a few times, same thing keeps happening, is there anything else I can try before I chalk it up to hardware malfunction and send it in to get a new one.... i reaallly dont want to do that
im also tried different sd card, and none of them have worked.

Ted926 said:
i have a few times, same thing keeps happening, is there anything else I can try before I chalk it up to hardware malfunction and send it in to get a new one.... i reaallly dont want to do that
im also tried different sd card, and none of them have worked.
Click to expand...
Click to collapse
Well..... I wouldn't consider it to be a hardware malfunction yet.
1. Have you tried a non-apps2sd rom, like Stock Froyo
2. Have you tried completely reformatting your SD card on your desktop, while using a MicroSD to SD to USB converter or something of that sort. You'll need to delete all the partitions as you won't be able to see the EXT partiton in explorer, use disk manager
3. Have you tried using a different SD card?
4. Maybe you should completely wipe all the device in fastboot, maybe something is screwy, maybe even reinstall your recovery image
Try these things, then come back with results. We can diagnose issues after some of these troubleshooting techniques

i haven't tried formatting the card, but i have tried other cards with the update.zip flash, do you have a link to the stock froyo file
i think the problem is that the one i downloaded wasnt legit, and i have wiped the device in fastboot, the problem is that something is wrong with the touch screen, when it relaods from rebooting, it will get to the touch the android welcome screen and wont register any touch screen input, only volume up/down, trackball, and power button

okay, i tried formatting the sd card, and putting the update.zip file on it, and the same error occurred, when i tried to flash in recovery mode.

any update on what i can do to fix this?

Flash the original recovery image. You can find it http://forum.xda-developers.com/showthread.php?t=614057
You would do this through fastboot. Its easy, try that out

how do you do it through fastboot, i've only flashed through recovery

Ted926 said:
how do you do it through fastboot, i've only flashed through recovery
Click to expand...
Click to collapse
Put the img file on your sdcard, boot into fastboot, it should automatically check for the image and you should get a prompt asking for you to continue installing the image

no luck, it doesnt search for the image. When i enter fastboot, it just shows four options: bootloader, reboot, reboot bootloader, and power down

Ted926 said:
no luck, it doesnt search for the image. When i enter fastboot, it just shows four options: bootloader, reboot, reboot bootloader, and power down
Click to expand...
Click to collapse
Then I would say something is faulting with your SD Card or your SDcard slot. I would try and take a very small ammount of rubbing alcohol and a q-tip to the contacts of your SD card, but there is no way to get into the slot without damaging it. If you have to do a warranty replacement just state that yes your device is bootloader unlocked but you're a developer and it is necessary to unlock in order to better serve the android platform

Stuck at S screen - tried everything with no results

This is yet another thread on an GT I9000 stuck at boot, but with a twist!
The diference is that it hapened without me doing anything to it. No flashing roms, no rooting, no unlocking, nothing.
One day it turned itself off, turned on again, get pass the initial screen, gets pass the carrier animation, and it is stuck at the big shiny S screen.
I'm not new to XDA or to flashing (old windows mobile), so I decided to come here and look as usually I can find my answers. The thin is it seems no one else has a similar problem! Not here nor the entire web!
I've been searching and experimenting (it doesn't work anyway, so it is ok to test every solution) for 2 consecutive weeks and still nothing!
I am able to get into download mode, into recovery mode, I am able to flash rooted (or rooting) kernels, I can do everything (except update from SD card with Cyanogenmods, it always says the file is BAD).
I've flashed stock roms, following all the procedures, with Odin, with Heimdall, I've tried everything suggested by "Android Solutions" but nothing!
I'm really frustrated, so I'm reaching to see if there's someone that can shine some light on how to solve this... I feel I'm about to smash the thing with a hammer! (but this won't solve the problem, right...)
Thank you in advance
G

GAlves said:
(except update from SD card with Cyanogenmods, it always says the file is BAD).
Click to expand...
Click to collapse
I assume you had rooted and had CWM when trying to flash CM from SD cards? if not, it will not work, using 2e or 3e recovery
First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card....Do remember to backup your contacts, data, images etc and also your EFS folder before flashing a ROM and make sure you have more than 50% battery charge before you attempt any sort of flashing.
Also assume you had tried everything in My Android Solutions did not get you out of bootloops?
so, boot into CWM > mounts and Storage> to copy your entire SD card to PC, after which you should format every partition (you will in-effect lose everything by doing this,) and do not reboot
after this, you must pull out battery and powerup into download mode to flash JVU+Root ROM with 512 PIT (repartition and update boot loader ticked in odin3) from My Android Collections

Hi xsenman,
Thank you for the reply.
in fact, I tried to CM from the SD card after having flashed CWM rooted kernel with Odin, but at this point the phone was not booting anymore. The whole reason I wanted to flash it in the first place was because it started bootlooping by itself while completely stock.
So I came here to xda, and follewed the instructions. I thought it would be a simple matter of flashing with a new rom and everything would be a-ok. It didn't.
I've tried every single trick mentioned in "my android solutions" (great information repository by the way, lots of work there) and still nothing. Today when I get home (forgot the phone at home) I'll flash the stock everything and try to follow the SD format procedure you mention.
I'll post back
Cheers
G

Hi again,
I've tried xsenman's suggestion and still nothing.
I could understand if this was a SD card error (because it was damaged in some way), but I have no indication of a SD card error. It can read everything and I even can see the file structure inside the SD card (and I do not mena the external SD card ofc). I was even able to copy some files to and from it!
I think I'll "fix it" with a big hammer and buy me an iphone! This is soooo frustrating!
anyone has any other ideas? I'll try anything and everything.
Cheers
G

GAlves said:
in fact, I tried to CM from the SD card after having flashed CWM rooted kernel with Odin, but at this point the phone was not booting anymore.
Click to expand...
Click to collapse
CM needs to be flashed twice, try this method or this
Check Here to chose your forum/Guide by Version of your phone or you will have more problems by using wrong solutions due to different versions of Galaxy S
Use only ROM and solution for your model and Wipe x3
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card....
(Do remember to backup your contacts, data, images etc and also your EFS folder before flashing a ROM and make sure you have more than 50% battery charge before you attempt any sort of flashing.)

Hi again,
Tried everything and got always the same result. Nothing.
Maybe the problem was with some piece of hardware (but I find it strange). As I said before I firstly tried to flash it because it had come to a bootloop by itself so maybe it had a deeper problem.
Now I got it solved. I bought me a brand new iPhone 5 (LOL) and flashed a stock rom on the SGS and sent it to the carrier customer support. It had one year guaranty. Lets see what they say about it.
If they can solve it I'll have 2 very nice phones!
Thank you anyway for you help.

Had same problem some time ago.
THIS should help you too

Hi again!
I had tried that too, and the result was the same as all the other things I've tried. Nothing.
Today I had some feedback about the phone (I sent it to repair). The phone is on its way back to my hands, and the repair status says:
"Software update and power circuit repair. Tested OK".
Let's see if it does tests ok when I get it back!
Two weeks ago I got an e-mail from the tech support asking what was wrong with the phone because they could find nothing wrong with it. I asked them to turn it on and try to make a phone call for example, or connect to a wi-fi network. It doesn't really matter, I just wanted them to try to do something that involved turning it completely on and use the device in any way they wanted. Clearly they hadn't even tried to turn it on. Otherwise they would have figured out that there was a problem...
This was the carrier support, not Samsung (I think). Anyway it SUCKS bigtime!
Now I need to figure out what to do with it...
Thanks anyway for your support!
Cheers
G

Just to let people know how this ended up.
My SGS i9000 went to the repair shop for two times. The first they replaced the charger plug, the second they say they replaced nothing (but I don't belive them )
As I still think this was some sort of issue with the samsung firmware, I just flasher CM10 and it's been stable since then.
My girlfriend got it as a present and she's quite happy with it!
Thank you all for the help!

[Q] i897 Internal SD card unmountable and flashing ineffective

I've never used a forum before, but I'm having a very tough time with my i897 captivate. Its previous owner left it in a box while software updates passed it by. When I came in possession of it, I used rooting, custom ROMs, and flashing to update it to more useful firmwares. I mainly stuck to CM 7, 9, and 10. Eventually I fell victim to that "ICS Encryption Unsuccessful" error and clicked reset, triggering a period of bootloop. I've since fixed the bootloop issue but I still can't get my phone to boot to any firmware. Over the past year, I've been trying all sorts of things to get my phone to work again and I don't know if I've made the problem worse or not. I can get my phone to boot the At&t screen, download mode, and whatever recovery kernel I'm on at the time, but nothing more. I don't even think I have a ROM installed anymore.
What I've tried:
several Odin One-clicks
Heimdall One-click unbrick
Partitioning my external sd card to act as an internal one
ADB sideload
ADB push and install zip from sd card
The errors I run into the most are the "can't mount sd card" ones when I'm trying to flash a custom ROM in recovery. I guess my internal sd is corrupted somehow? Is there a way for me to fix this mess?

asertap said:
I've never used a forum before, but I'm having a very tough time with my i897 captivate. Its previous owner left it in a box while software updates passed it by. When I came in possession of it, I used rooting, custom ROMs, and flashing to update it to more useful firmwares. I mainly stuck to CM 7, 9, and 10. Eventually I fell victim to that "ICS Encryption Unsuccessful" error and clicked reset, triggering a period of bootloop. I've since fixed the bootloop issue but I still can't get my phone to boot to any firmware. Over the past year, I've been trying all sorts of things to get my phone to work again and I don't know if I've made the problem worse or not. I can get my phone to boot the At&t screen, download mode, and whatever recovery kernel I'm on at the time, but nothing more. I don't even think I have a ROM installed anymore.
What I've tried:
several Odin One-clicks
Heimdall One-click unbrick
Partitioning my external sd card to act as an internal one
ADB sideload
ADB push and install zip from sd card
The errors I run into the most are the "can't mount sd card" ones when I'm trying to flash a custom ROM in recovery. I guess my internal sd is corrupted somehow? Is there a way for me to fix this mess?
Click to expand...
Click to collapse
sd card issues are usually due to kernel, have you tried flashing a custom one to boot in recovery?
If your internal is dying, partitioning an external sd should work but since it's still not fully booting, I feel like that's not the issue. I had that happen to mine, tried many Odin and Heimdall, when finally one Heimdall worked (after like 10-15 different attempts). Shortly after my internal died though.
So I would start by flashing a kernel with Odin 1.7, see if you can boot in recovery (always took me a few attempts to get it). From there you can flash a custom ROM (I always suggest GamerzROM for the cappy but really it's personal preference). Otherwise, your 2nd option is bashing your head on Odin/Heimdall one-clicks lol
PS.: Just came across this if all else fails: http://forum.xda-developers.com/showpost.php?p=61479845&postcount=58

I have this exact same issue... Thank god I'm not alone! I wondered what that stupid "encryption failed' message was all about.
So I've done just about everything the above has done, except the problem is I continue to get a boot loop. The ODIN one-clicks all boot loop. Ive been able to install a custom kernel and CWM, and surprisingly my internal storage is still accessible, but when I try to install the CM9 that's on there it freezes at "opening update package".
So, stuck between a rock and a hard place. I can't put any other ROM's on the internal storage because I have no way of accessing it. Therefore I have to rely on a ODIN one-click. All of which boot loop or just fail outright. Is there a way to access the internal storage without fully booting android?

P9-L09/19 touch screen doesn't work in eRecovery or TWRP

Hi,
I must admit that I am panicking now because looks like i have bricked my phone and no matter what i try to do i am stuck between erecovery fastboot and TWRP.
To give you some light as to what actually happen... I've replaced oeminfo in originally EVA-AL-10 with EVA-l09. I have installed full system EVA-L09C432B136 and everything was fine at that point.
I thought to myself that it would be nice before putting any data to the phone to actually rebrand it to L19 so i do get a dual sim support.
In another thread I've found oem info for L19-C432. I've replaced it and decided to reflash full image EVAL19-C432B161 which i've also found on this forum due to huawei servers being down? (for some reason I couldn't download anything from the manufacture sources) This is when i got a first error message that updated failed due to incompatibility with the device.
I have been looking for some other full packages but whichever one I've put on a SD card, i couldn't get to work. for some stupid reason i thought about updating B136 hoping that during update process incompatibility issue will get fixed. Unfortunately this wasn't the case and even though the update completed "successfully" on the screen, after the reboot, i ended up in eRecovery.
Having oeminfo in SRK tools which worked for me previously i unlocked bootloader again and installed TWRP so i can root my phone and use srk to update OEM info back to 09.
This is where serious problems started to happen. in TWRP I am unable to use touch screen, only volume buttons and power button to confirm. As its a first launch of the TWRK I cannot even swipe to confirm read/write mode hence I can't go any further to install supersu etc...
Do you have any suggestions what can I do to unbrick it? Is there any workaround to get root via sd card? or maybe forcing somehow stock rom L09C432B136 to install regardless? Maybe there is a way to repack update.app so i doesn't look at the oeminfo?
I have tried replacing images (CUST, BOOT, RECOVERY and SYSTEM) in fastboot mode but I am not having any luck whatsoever.
Please throw me any ideas...
Thanks.

Hi azgooon,
I'm having the same problem, even it's a different huawei phone, did you get your problem fixed? How? Thanks for sharing.
douyi

Device bricked after flashing the wrong software version file, cannot get unlock code

Hello,
I tried to update my P9 (German Vodafone version (EVA-L09), I think software version was B137), using the method described at http://ministryofsolutions.com/2016...ui5-0-full-firmware-b339-europe-vodafone.html
Now I am stuck at a boot loop as I flashed in the wrong order, I first flashed the update.app (seems to be the data file) with success, then the phone rebooted and I got into the loop. I tried various things, I tried to got back to the previous version, I tried to flash stock version, I tried to flash the other file I downloaded from the website, but all failed. When I try to get into fastboot it says locked for both lines, and HiSuite tells me it has no software version for this phone version to repair the phone.
Is there any way to get the phone unbricked?
Update: The last thing I did was trying the rollback again, now the phone is stuck at the logo, it is getting very warm and I cannot turn it off, it just reboots again when I try to turn it off. I think it is finally broken, I will wait until the battery is drained (who invented phones with batteries you cannot pull anyways...)

It still can be recovered, however, I dont know the finer details of it. There has been a lot of threads in the Q&A section about people stuck in the current situation as you. However, I think most has been able to get back to get out of the bootloop by using DC-Phoenix\DC-Unlocker.

Been there. Put in fridge till it runs flat and stops heat damage.. Plug in PC to charge. It very likely will not charge fully as the system is borked but mine did enough to get to Fast Boot Recovery. From there use the SRK Tool to install TWRP and then wipe the system so have no remains of failed nougat, B300 or Marshmallow - no OS. Then install stock recovery using SRK tool. Load a stock rom to SD card. Use the Paul O'brien C432B136 rom. Switch off and three finger reboot to SD card update. Should be good.