Hello,
My Ascend P1 seems to be soft-bricked, the phone turns on and I can access CWM Recovery... or so it seems. It all started when my phone's battery died and right after that, I put it to charge and left it alone for around 4 hours. When I came back, it hadn't charged at all, I tried to turn it on and it would get past the Huawei Logo and pass to the LiquidSmooth ROM launcher screen, however, it would just freeze and restart the phone. It fell in what I heard is called a bootloop.
I did some research here and there and found a lot of tutorials about how everything is done from the scratch. I did the basics, clear cache, dalvik-cache, factory-reset, etc, but when I tried to install the ROM from the SDCard, the installation finishes way too fast (15 seconds at most), almost as if it did nothing (which I believe it's true).
I also tried to install a new recovery through a tool called Shaume, it seemed to be working at first; I installed it (which took probably like 3 seconds to install), it launched the "new recovery" and everything about seemed to work just fine, however, when I first did this I had forgotten to put the ROM in my SD Card so I took it out, put the ROM in it and to make sure, I restarted the phone. After it restarted, it went back to the old CWM I had installed (this one has no touchscreen features) and it seemed as if everything I had done was for naught.
I just don't know what to do anymore. I tried to take a look at the logs after trying to format /data, /cache and such, and the most notable thing I saw there was "rm: can't remove '/data/dalvik-cache/' read-only file system", this same "read-only" happened referring to some of the applications I had installed before.
I am no expert in this matter, as I myself have never even rooted/flashed ROMs (the phone was already rooted/flashed when I got it). At least, through all of the research I've done it seems that as long as the phone is able to get to the Recovery, it's not something that cannot be fixed.
I really hope you can help me fix this.
Thanks in advance!
I'd try to Flash Stock firmware before trying again.
I am requesting to have this thread move to the right forum so that the right experts may be of help.
Oh, I'm really sorry. I'm totally new in this forum and thought this was the correct section for this thread.
Sorry, again. And thanks for your help.
I like some solution?
SairoJ said:
Oh, I'm really sorry. I'm totally new in this forum and thought this was the correct section for this thread.
Sorry, again. And thanks for your help.
Click to expand...
Click to collapse
I tried with all tutorials and I have not accomplished anything
Related
Hey peoples,
Just wanted to say hey and thanks for all the hard work you obviously put into this phone, it is pretty amazing.
I have had the phone for about 2 weeks now.
It is my first Android based phone and my first smart phone.
I really want to be able to use tethering and so I have decided that it is worth it to me to root the phone and try my hand at making it work.
So, I have been reading for the last week, trying to digest all of the information and really trying to wrap my head around just how to do this the right way.
Here is what I have done, and how I have succeeded and failed.
I downloaded the following:
PC36IMG.zip
EVO-recovery.zip
and placed PC36IMG.zip in the root of my sd card.
Went through the motions and successfully flashed from within the bootloader of the Evo.
Rebooted as instructed.
Now, here is where I got lost, or really was unable to confirm if I was successful or not.
I extracted the EVO-recovery.zip file to a folder I called "evo".
I placed that folder in the root of my c drive.
I opened up a command prompt and typed "cd \evo" and confirmed I was in that directory.
From there I typed "adb reboot recovery" and hit enter.
Then, once that process started, I opened up the evo folder and double clicked "recovery-windows.bat".
The process seemed like it was doing what it should be doing, and once it was complete, I navigated to and created a NAND backup.
That is where I think I went horribly wrong, as once that was done, and I rebooted the phone, I was shocked to find that all of my contact data was gone, which was painful because I had spent the last 2 days getting that all sorted out and new numbers transferred from my old phone (manually).
Anyway, after the initial shock wore off, I started looking around and realized I now had a blank phone.
All of the sprint apps were still there and nothing seemed to have changed other than my phone was now void of everything that I had installed and added to it.
So, feeling like I had probably rooted the phone, but failed to back up at the right point in the exercise, I really had nothing to lose since I was going to have to add all that data again anyway.
That brings me to today.
After much reading, and poking around, I figured all I really had at this point was a rooted stock rom on my phone?
I could not find any super user app in my apps pane, nor any other indication that I had done anything in particular other than wiping my phone clean.
So, I then decided that I needed to install a custom rom.
That seemed like the logical next step.
So I downloaded "RvU_1.3.2.zip" from Android central.
I placed that file on my sd card, shut the phone down, and then powered it up while holding the volume down key.
I navigated to and flashed the file to the phone and was ultimately stuck in infinite (reboot) loop after the process was seemingly complete.
In a bit of a panic, I pulled the battery, and rebooted the phone with the volume key depressed, and from there I wiped the caches (delvic and cache) and reset to factory default within the same menu.
From there, I went in to restore mode and restored to the NAND back up I created.
Now I was back in the same spot prior to trying to flash the RvU_1.3.2.zip rom.
Feeling a bit deflated, I decided that I really needed to see if I could get the phone back to factory fresh stock condition and was successful using "RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_release_171253_signed.exe" which I downloaded from a link on this site.
So,
If you are still with me after this long winded post, and are even remotely interested in helping me figure out where I went wrong in the process, I would really appreciate any help you may offer.
At the end of the day, I would really like to root this baby, get a rom which has all of the Sprint crap ware deleted and ultimately be able to tether my laptop.
Is anyone interested in helping an old guy out?
Thanks in advance, this seems like a place with a hell of a lot of knowledge and skill.
I appreciate being here.
First off, your contacts should have been saved when you first created a google account when you got the EVO. After you completed part 1 of the root process, when you reboot your phone, you should gotten a prompt if you wanted to sign in to google. Since you are an existing customer, sign in, and within minutes, your contacts will show.
Second, it is highly recommended that you do part 2 of unlocking Nand protection so that you don't have to do extra steps to get into recovery mode and can get into it from within android.
Also, the blank phone that you saw was/is completely normal, since when you flashed the pc36img file, it ultimately erases all user data on the phone.
Ok, thanks Dave,
So, in your opinion, was I successful in rooting the phone?
And where did I fail in trying to get a custom rom installed?
Seems like you did it just fine. Try flashing the custom rom again if you'd like. Otherwise, go for the gold and do part 2 of unlocking nand protection.
-------------------------------------
Sent via the XDA Tapatalk App
I lov using my phone explorer app, Everything works great except I used to be able to control my phone using my PC keyboard n mouse in the phone view.
I've upgraded my my phone to CM7 and it give an option to select My phone explorer as an external keyboard.
I cant get it working without selecting the option of external text in the appropriate input on my phone which sort of defeats the whole remote angle.
Can anyone help please ....
Bootloop solved
I read this thread trying to figure out why my phone (marvelc A510c virgin mobile) went into bootoop after trying to installing simonsense3.5 rom, and thought I'd share my success story. This is actually my first post. I want to hopefully save someone like me HOURS of heartache over a stupid solution.
Background (roughly):
Unlocked bootloader via htcdev, worked great.
Used Simonsimon34's htc utility and it worked okay. I still had to use the htc supertool to get root.
Got cwm 5.0.2.8 installed and made a backup rom
Downloaded simonsense3.5 rom and attempted to flash it, but phone hanged in recovery. After that, I was stuck in a bootloop. Could still get into recovery, but cwm would hang ALL the time doing things like wiping and I couldn't get it passed "Opening Update Package" when flashing new roms. I read forum after forum, reformatted my sd, wiped partitions, got a second sd, tried 3 or 4 roms people swore would work, did it all over again. Nothing! I found a thread that said to back cwm down to 5.0.2.6, but that didn't work. This went on for two days and I was getting desperate.
SOLUTION:
I finally found a thread (http://forum.xda-developers.com/showthread.php?t=1213229) that posted cwm 4.0.xx (the "previous version" link) and at my wits end flashed that, and wouldn't you know it, success! CWM was the problem the whole freaking time! I used the cwm partition creator to make a fresh 1024b partition on a fresh sd, wiped everything, put the rom on, and installed simonsense3.5 on the first damn try. The rom works okay, but I'm having some bugs... but that is another forum.
Good luck!
Hello guys, this is the first time I am posting anything so if I am doing anything wrong, sorry just say what it was and I will try to correct it. Well due to some unfortunate events I needed to get my GSM Galaxy nexus running again, I rooted it a long time ago when I was trying to get into roms and mods, but I had to leave that aside due to some other projects that demanded a little more attention at the time. Since my device was having some battery problems I thought that by updating it the problem could be fixed, at the time it was running CyanogenMod 10.2.1 if my memory is right. I went into the update tab under settings in the phone itself and tried installing CM11 from there. the phone prompted me if I would like to do it and I hit yes, it booted into CWM and it proceeded with the installation. But then it gave the status 7 error and the instalation could not be completed (from what I've read this problem happens when the device is not the one compatible with the Rom being installed, I went in the script and checked it, but it was maguro the same I had used for some time , since my device is a GALAXY NEXUS GSM model. Well I went to bootloader again and then do CWM and found the Rom I was using earlier (the CM 10.2), I flashed it and it was all "nice" and working but the battery was discharging way too fast and I tried it again but this time, for some reason (some times I do stupid things) I deleted some folders from the inumerous 0/ folders my device was accumulating and the CM 10.2 was among them. After I that I tried flashing another CM 11 Rom, an older one to try and see if it went well. sigh.... It did not. The same problem occured and now I cannot flash the working Rom. The Phone boots but it does not get past the google logo and then turns off and boots again going directly into CWM , I tried using Wug Fresh's Nexus Root Tollkit, but since I can't go into the settings of my phone I can't configure the drivers properly and if I try to use the Flash Stock + Unroot option with soft-Bricked/Bootloop option checked it returns that a fastboot device was not found. And hence I can't do anything else. Well I don't know what to do and my knwoledge is fairly limited, so anything can help. I have already searched some solution in other treads but none have given results. Does anyone can guide me where to look or some thing I should do?
Thank you very much for any time spent helping.
Hi,
I will have your thread moved to your device section so the experts who own your device can help.
Good luck!
After tinkering with my Androids over the years, (Infuse, Captivate, G2, and now G3) I have finally decided to become a member of the forum that I primarily use as a source of information and links to downloads. I'd like to first say thank you to all those that have unknowingly help me over the years with my roots. Great place you've got here.
Now the fun part, after two days of ownership, I have experienced the first issue was not able to resolve on my own, what appears to be a hard brick. I downloaded Flashify after my initial root, installed TWRP Manager, ran the patch for writing to the SDcard, and installed TWRP Recovery from AutoRec. All appeared to go well and it said the instal was successful. I followed the instructions I found online that had great results for my particular model and version 5.0.1. Well, when I went to boot into recovery to make my initial backup, the phone shut down and would not come back up. No response at all. It wont power up by any method, tried letting the capacitors drain, still no go. After tinkering with it for a few hours (I've owned this phone for a total of 2 days now), I finally came to the conclusion that it would need JTAG and the original boot image flashed over the one that I mucked up.
Any ideas on where I made my mistake? I'm near 100% certain I downloaded the proper files for my phone model.
Also forgot to mention, I have not changed anything else on the phone. Only installed apps and root browsers I planned on using. So stock kernel, stock ROM, nothing until I started getting ready to make myself a save point, ironic really!
jamguitarist said:
After tinkering with my Androids over the years, (Infuse, Captivate, G2, and now G3) I have finally decided to become a member of the forum that I primarily use as a source of information and links to downloads. I'd like to first say thank you to all those that have unknowingly help me over the years with my roots. Great place you've got here.
Now the fun part, after two days of ownership, I have experienced the first issue was not able to resolve on my own, what appears to be a hard brick. I downloaded Flashify after my initial root, installed TWRP Manager, ran the patch for writing to the SDcard, and installed TWRP Recovery from AutoRec. All appeared to go well and it said the instal was successful. I followed the instructions I found online that had great results for my particular model and version 5.0.1. Well, when I went to boot into recovery to make my initial backup, the phone shut down and would not come back up. No response at all. It wont power up by any method, tried letting the capacitors drain, still no go. After tinkering with it for a few hours (I've owned this phone for a total of 2 days now), I finally came to the conclusion that it would need JTAG and the original boot image flashed over the one that I mucked up.
Any ideas on where I made my mistake? I'm near 100% certain I downloaded the proper files for my phone model.
Also forgot to mention, I have not changed anything else on the phone. Only installed apps and root browsers I planned on using. So stock kernel, stock ROM, nothing until I started getting ready to make myself a save point, ironic really!
Click to expand...
Click to collapse
Post the guide that you followed
You would have to kick your phone into Qualcomm USB Loader 9008 in order to fix it
http://www.androidbrick.com/unbrick-recover-your-dead-lg-g3-all-variants/
Soft bricked G3 with a lost IMEI number
Hey guys I have 2 major problems for my phone.
1) I was trying to flash Marshmallow 30B stock ROM yesterday, so I was told to install a few files. New system file, new modem file, new boot file and SuperSu BETA v2.65. I tried and tried many times yesterday, but unfortunately it didn't work. So I was like "okay fine, let's just use some custom ROM from XDA."
I chose the XenonHD 6.0 Experimental ROM and copied into my internal storage along with my gapps they recommended. I booted up into recovery mode, backed up the installed ROM and factory reset it. I went to flash my ROM first then my gapps. But then halfway flashing the log display showed this:
HTML:
unmount /system failed: No such volume found
updating partition details...
Then it ended saying it was successful and it continued on flashing the gapps and so on. Surprisingly no "unmount /data failed or anything, just the system that is acting up. After finishing flashing all the file, I went to reboot my device. At first it showed the LG logo as usual, then the screen became black. I went online and search all about this unmount system problem, and all they say is that I have to wait for about 10 minutes then the Android logo will come on. So I waited for 15 minutes? (I have an iPad mini beside me counting down the minutes). I came back the whole phone is still black screen, the whole screen is turned off, not idle blank screen. I started to freak out and I took out the battery and put it back again and went into recovery mode.
2) Another problem is this IMEI number loss, I don't know how I got lost this information. I'm not sure if my EFS file is corrupted or not. I realized it because I was receiving no cell signal while I was in the city central. Unfortunately I don't have a backup of the EFS file ( I don't even know if I have it ).
Please help me solve these problems. It's happened for a few days now.
mrchuajason said:
Hey guys I have 2 major problems for my phone.
1) I was trying to flash Marshmallow 30B stock ROM yesterday, so I was told to install a few files. New system file, new modem file, new boot file and SuperSu BETA v2.65. I tried and tried many times yesterday, but unfortunately it didn't work. So I was like "okay fine, let's just use some custom ROM from XDA."
I chose the XenonHD 6.0 Experimental ROM and copied into my internal storage along with my gapps they recommended. I booted up into recovery mode, backed up the installed ROM and factory reset it. I went to flash my ROM first then my gapps. But then halfway flashing the log display showed this:
HTML:
unmount /system failed: No such volume found
updating partition details...
Then it ended saying it was successful and it continued on flashing the gapps and so on. Surprisingly no "unmount /data failed or anything, just the system that is acting up. After finishing flashing all the file, I went to reboot my device. At first it showed the LG logo as usual, then the screen became black. I went online and search all about this unmount system problem, and all they say is that I have to wait for about 10 minutes then the Android logo will come on. So I waited for 15 minutes? (I have an iPad mini beside me counting down the minutes). I came back the whole phone is still black screen, the whole screen is turned off, not idle blank screen. I started to freak out and I took out the battery and put it back again and went into recovery mode.
2) Another problem is this IMEI number loss, I don't know how I got lost this information. I'm not sure if my EFS file is corrupted or not. I realized it because I was receiving no cell signal while I was in the city central. Unfortunately I don't have a backup of the EFS file ( I don't even know if I have it ).
Please help me solve these problems. It's happened for a few days now.
Click to expand...
Click to collapse
i don't claim to be an expert in this field, but there are two things that come to mind that you could look into, maybe ask more experienced ppl on those threads.
it sounds like some sort of partition problem, or corrupt data, maybe you flashed a bad file or a file for another rom.
you could try manually formatting drives in command terminal without mounting them
also unbricking might work too but if your hopes and dreams are in this phone then talk to someone who knows more than me because i wouldn't bet my bankroll on these just suggestions for you to look into. I feel like the guys that write those guides probably can answer your question better and with more confidence.
KronicSkillz said:
i don't claim to be an expert in this field, but there are two things that come to mind that you could look into, maybe ask more experienced ppl on those threads.
it sounds like some sort of partition problem, or corrupt data, maybe you flashed a bad file or a file for another rom.
you could try manually formatting drives in command terminal without mounting them
also unbricking might work too but if your hopes and dreams are in this phone then talk to someone who knows more than me because i wouldn't bet my bankroll on these just suggestions for you to look into. I feel like the guys that write those guides probably can answer your question better and with more confidence.
Click to expand...
Click to collapse
I don't quite know how to do it though but I've been thinking about unbricking my phone and restoring to factory state and start all over again. Do you mind posting a link for the instruction on how to do all this? Thanks
I have the same problem,and i resolve it,try this
http://forum.xda-developers.com/lg-g3/development/stock-d855-30b-images-kdz-flashables-t3282012
---------- Post added at 11:33 AM ---------- Previous post was at 11:31 AM ----------
I have the same problem,and i resolve it,try this
http://forum.xda-developers.com/lg-g...ables-t3282012
KronicSkillz said:
i don't claim to be an expert in this field, but there are two things that come to mind that you could look into, maybe ask more experienced ppl on those threads.
it sounds like some sort of partition problem, or corrupt data, maybe you flashed a bad file or a file for another rom.
you could try manually formatting drives in command terminal without mounting them
also unbricking might work too but if your hopes and dreams are in this phone then talk to someone who knows more than me because i wouldn't bet my bankroll on these just suggestions for you to look into. I feel like the guys that write those guides probably can answer your question better and with more confidence.
Click to expand...
Click to collapse
mimivg said:
I have the same problem,and i resolve it,try this
http://forum.xda-developers.com/lg-g3/development/stock-d855-30b-images-kdz-flashables-t3282012
---------- Post added at 11:33 AM ---------- Previous post was at 11:31 AM ----------
I have the same problem,and i resolve it,try this
http://forum.xda-developers.com/lg-g...ables-t3282012
Click to expand...
Click to collapse
This was the ROM I initially wanted to flash. I think something went at flashing the Modem causing my phone to have this unmount /system problem.