Related
So I used to run the CM7 rom, then upgraded to a ISC WIP. Well, it was pretty unstable, and wanted a stable rom, so tried restoring my old CM7 backup, and now when I turn on my phone, it shows the HTC splash screen, the goes black (screen still on), and won't go past that. I realize now I downgraded the firmware, and you can't do that.
My buddy said I need to get some toolkit and reset EVERYTHING back to stock roms, re-root and all that. So can some generous person link to all that? I see a lot of it in the Inspire 4G forums, but want to make sure I have it all. And after I flash all the stock stuff, can I restore that CM7 backup (clockwork recovery mod)?
Thanks in advance for the help/reply, much appreciated.
If you can get into hboot, this may help you:
http://forum.xda-developers.com/showthread.php?t=1396229
pazzo02 said:
If you can get into hboot, this may help you:
http://forum.xda-developers.com/showthread.php?t=1396229
Click to expand...
Click to collapse
That's what I was looking at, wasn't 100% sure if it's the right tut for me. Thanks for the reply!
Do I need to reinstall recovery, or flash the stock rom?
Oathdynasty said:
Do I need to reinstall recovery, or flash the stock rom?
Click to expand...
Click to collapse
You should follow the steps to reinstall recovery, then go to flashing a rom. You only need to go through the "flashing a stock rom" section if you had problems reinstalling recovery. Just read through all the steps and you'll get it.
Oathdynasty said:
Do I need to reinstall recovery, or flash the stock rom?
Click to expand...
Click to collapse
If you are S-OFF you just can flash a new recovery image and then flash any rom you want. You will have to do it from command prompt...
if you need help in doing that, just let me know...
glevitan said:
If you are S-OFF you just can flash a new recovery image and then flash any rom you want. You will have to do it from command prompt...
if you need help in doing that, just let me know...
Click to expand...
Click to collapse
I could use some help haha. I tried downloading the stock rom (PD98IMG.zip) from multiupload, but it'd down, and the mirror says it'll take several hours.
Oathdynasty said:
I could use some help haha. I tried downloading the stock rom (PD98IMG.zip) from multiupload, but it'd down, and the mirror says it'll take several hours.
Click to expand...
Click to collapse
Look in the second post in that thread. The OP noted last month that there were probs with multiupload and posted an alternate dl.
pazzo02 said:
Look in the second post in that thread. The OP noted last month that there were probs with multiupload and posted an alternate dl.
Click to expand...
Click to collapse
I got it. I went on the cyanogenmod irc, and they helped me. I didn't have to flash anything stock, I rebooted into my bootloader, went into recovery, wiped system, data, dalvik, cache.... All that, flashed cm7 and restored
Sent from my Desire HD using Tapatalk
Good. Glad you got it fixed
Oathdynasty said:
I got it. I went on the cyanogenmod irc, and they helped me. I didn't have to flash anything stock, I rebooted into my bootloader, went into recovery, wiped system, data, dalvik, cache.... All that, flashed cm7 and restored
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Glad you got it sorted out, To be honest that is the first thing you do when a rom wont boot. Whenever you restore a backup it is best to wipe first
I tried to flash a aokp rom and before flashing made a back up. Now when I flashed the rom and rebooted the phone im stuck at samsung boot. I can get into recovery. At first it was a messed up recovery i tried to get to an old rom and reinstalled inimitable on reboot still stuck at samsung but can get into red recovery. Backup when reinstalling says cant mount system/! please help me asap I cant do anything I need my phone I am in panic mode.
Have tried reflashing The ROM again...or if you just want to go back to stock see my signature for links to the one click method
...btw your in the wrong section to post this...
The OP for aokp does state to flash twice...did you?...first time with wipes, then you can pull battery ...go back to cwm and reflash...again.
going back to stock is your way. clear all that crap out
http://forum.xda-developers.com/showthread.php?t=1524081
Post one to stock.....
Post two to put cwm back on....
Read with detail...the thread I provided....
Your probably going to need to go back to stock, but just so you know, flashing any ICS rom while on Gingerbread bootloaders will get you a "Messed up recovery" You'd have to flash ICS bootloaders, but doing that means you can't flash any non ICS roms, I personally still have a rainbowed recovery on the off chance I want to flash GB rom.
soulysephiroth said:
Your probably going to need to go back to stock, but just so you know, flashing any ICS rom while on Gingerbread bootloaders will get you a "Messed up recovery" You'd have to flash ICS bootloaders, but doing that means you can't flash any non ICS roms, I personally still have a rainbowed recovery on the off chance I want to flash GB rom.
Click to expand...
Click to collapse
We have no ics boot loaders...froyo boot loaders make the recovery look funky...gingerbread boot loaders fix that problem and can be used with froyo, gingerbread and ics ...not trying to be rude or a jerk just informing you
Sent from my SGH-I997 using XDA
Actually the "messed up" or rainbow recovery is from the lack of gingerbread boot loaders, just figured this out this morning when I attempted to flash aokp uniporn. Once I did the heimdall one click with bootloaders checked (gingerbread boot loaders) I was able to successfully flash the aokp rom and recovery works perfectly. Its really better not to reply when one does not know what they are talking about oh and I was still able to reflash a gingerbread rom as well although I probably won't go back to gingerbread again since aokp is the **** and runs super smooth
Sent from my SGH-I997 using xda premium
Please move this thread from the Development Section.
edit- Thanks for moving it.
Sorry about posting so quickly in wrong section. I just know the guys who post in here are pros. I used heimdall and everything is back to stock, no superuser. Should that be right, am I now not rooted? I havent tried to boot into recovery, but I think I have it still. Can I just follow root methods if I want to go back to root? Thanks again.
I my experiences, I've noticed our phones use a form of "Cumulative" Upgrade system, where You have to essentially go from Froyo to GB to ICS or things go haywire when you actually start using your ICS Rom..
I've tried using Heimdall to flash back to stock, but it doesn't seem to fix all my files from time to time, so I still use GTGs Ultimate Unbrick, and once it starts up as you're in Recovery Mode do a Factory Reset/Wipe Cache Partitions, it helps with not having the "Google Authentication Failed".
It's a long process from start to finish either way, so i figure save yourself the hassle for the long run and wipe it fresh...
I used heimdall without clicking the GB bootloaders checkbox. Upon reboot after sucessfully flashing everything, my phone shows the rainbow color thing then boots normally. I have no seen any issues other than that, however I only got it back up and running about an hour ago. I will see as the day progresses what happens. I just would like to know where I go from here to reacquire root priveleges. When I try to boot into recovery with the button combo I get a rainbow colored screen and nothing else showing, should I re-run heimdall with gb bootloaders box checked?
IME, one flash will lock on Samsung logo, 3 finger back to recovery, wipe everything, flash the rom again and flash the gapps and it would have been fine...
I have that happen everytime I have flashed an AOKP ics..it always works out fine..
Those instructions are in most of the OP's...
Its very important to read that and have an understanding of what exact steps there are before you just start flashing away...
drnecropolis said:
IME, one flash will lock on Samsung logo, 3 finger back to recovery, wipe everything, flash the rom again and flash the gapps and it would have been fine...
I have that happen everytime I have flashed an AOKP ics..it always works out fine..
Those instructions are in most of the OP's...
Its very important to read that and have an understanding of what exact steps there are before you just start flashing away...
Click to expand...
Click to collapse
Upon flashing the first time i did reboot into recovery but it was so buggy i couldnt see what to select. I am back to non rooted stock i believe now but when trying to get to recovery it just hangs on a rainbow like screen.
Sent from my SAMSUNG-SGH-I997 using XDA
Cjohns8792 said:
Upon flashing the first time i did reboot into recovery but it was so buggy i couldnt see what to select. I am back to non rooted stock i believe now but when trying to get to recovery it just hangs on a rainbow like screen.
Sent from my SAMSUNG-SGH-I997 using XDA
Click to expand...
Click to collapse
I would use the one click heimell run it twice on the 2nd time check the box for bootloaders....
bigjoe2675 said:
I would use the one click heimell run it twice on the 2nd time check the box for bootloaders....
Click to expand...
Click to collapse
It actually doesnt allow me to select it. The box is "greyed" out yet says phone connected and ready.
Cjohns8792 said:
It actually doesnt allow me to select it. The box is "greyed" out yet says phone connected and ready.
Click to expand...
Click to collapse
Aft your 1st flash...dont close program...but put your phone back into download mode again and then it should allow you to check the box...then..
You probably can't mount until you format system, data, and cache. I had this issue before as well, Go to mounts and storage and Format system, data, and cache and then try mounting again.
Axiomkid said:
You probably can't mount until you format system, data, and cache. I had this issue before as well, Go to mounts and storage and Format system, data, and cache and then try mounting again.
Click to expand...
Click to collapse
Can't access recovery, it just shows a full rainbow screen.
Cjohns8792 said:
Can't access recovery, it just shows a full rainbow screen.
Click to expand...
Click to collapse
my suggestion is do the method i mentioned..
I was pulling my hair out for a few hours last night trying to get my phone back to a functional state. Fortunately I was able to do so, but I have no idea what caused all of my problems. Here's what happened:
I was running CM10 on my HOX (from this thread) for awhile now. I was having a few issues with it that were annoying but I didn't want to change the ROM and have to restore everything. I then got a notification for an update to CM10.1 so I downloaded that and installed it. During this process I decided to do a Factory Reset in TWRP.
Once I was booted back into CM10.1 I was having all sorts of strange issues, but the biggest one was that I was unable to connect to my cell network and it kept prompting me to restart. I decided I would just install another ROM so I downloaded CleanROM JL Beta 1 (here) and the Bulletproof-1.0 kernel (here).
I booted into TWPR and proceeded to wipe everything (i.e. clicked all of the buttons under the 'Wipe' menu). I've done this before and haven't had any problems. I then proceeded to install the kernel. It went through the installer fine without any issues. When I tried to install CleanROM JL Beta 1 in TWRP it just kept giving me an error and wouldn't bring up the installer.
I went back and forth trying to install multiple ROMs and every single one would give me an error. I thought I was screwed because I couldn't install an OS on the phone. I also went ahead and installed the stock kernel hoping that would fix the problem but it didn't. I eventually decided on finding the RUU to get me back to bone stock.
I downloaded the 2.20 RUU and relocked my bootloader. I went through the RUU process and everything is fine now, except the fact that I have a stock, bloated phone again.
Was it the kernel that messed me up? I installed it after I wiped everything and I'm not sure if I was supposed to do it that way. I'd like to get back to something stable again but I am not sure if I am able to since I relocked my bootloader and installed the 2.20 RUU. Any help is much appreciated, thanks!
NEW ISSUE #1: I just tried to install the 4.1 OTA update from AT&T. I donwloaded the update and proceeded to install it, but after it restarted everything on my phone was erased and it was set back to factory default on 4.0.1. Now when I check for updates it tells me there are nor updates, the server is full, or 'HtcDm has stopped'. What the hell happened there?
NEW ISSUE #2: I went ahead and tried the OTA update again and now my phone won't turn on and shows no status LED light when plugged in. Back to Best Buy it goes. I need a Nexus...
If you are S-on, did you remember to extract and flash boot.img seperately for each of the ROMs you tried?
Now combo of CleanROM JL and Bulletproof should have worked fine. Don't know what happened there. How did you flash Bulletproof? Using recovery or fastboot?
redpoint73 said:
If you are S-on, did you remember to extract and flash boot.img seperately for each of the ROMs you tried?
Now combo of CleanROM JL and Bulletproof should have worked fine. Don't know what happened there. How did you flash Bulletproof? Using recovery or fastboot?
Click to expand...
Click to collapse
I am S-ON and I did not flash the boot.img via fastboot at first, but then tried that after the ROM wouldn't install. I flashed the Bulletproof-1.0 kernel via TWRP.
afrat said:
I am S-ON and I did not flash the boot.img via fastboot at first, but then tried that after the ROM wouldn't install. I flashed the Bulletproof-1.0 kernel via TWRP.
Click to expand...
Click to collapse
You can't flash kernels in recovery with hboot 1.14 and S-on.
Not sure what you mean by "after the ROM wouldn't install" (the exact sequence of ROM flashing versus flashing boot.img using fastboot). But what you are describing is sounding like ROM-kernel mismatches.
redpoint73 said:
You can't flash kernels in recovery with hboot 1.14 and S-on.
Not sure what you mean by "after the ROM wouldn't install" (the exact sequence of ROM flashing versus flashing boot.img using fastboot). But what you are describing is sounding like ROM-kernel mismatches.
Click to expand...
Click to collapse
I followed the instructions given in the Bulletproof-1.0 post that said to install the zip via TWRP. I did that and everything went fine. I then tried installing CleanROM JL Beta immediately after and it would just give me the zip error.
What I mean by "after the ROM wouldn't install" was after it wouldn't install via TWRP. I then went back and extracted the boot.img, flashed it with fastboot, then went back into TWRP to try and install it again. That didn't work.
redpoint73 said:
You can't flash kernels in recovery with hboot 1.14 and S-on.
Not sure what you mean by "after the ROM wouldn't install" (the exact sequence of ROM flashing versus flashing boot.img using fastboot). But what you are describing is sounding like ROM-kernel mismatches.
Click to expand...
Click to collapse
In op it says he flashed kernel then rom, the rom would have overwritten the kernel flash if thats the order he did it in wouldn't it have? Im thinking it was a bad Cleanrom download he was trying to flash since it gave an error in recovery when he tried to flash it and wouldn't load it at all. Or maybe a bad TWRP image? Just guessing here.
eraste said:
In op it says he flashed kernel then rom, the rom would have overwritten the kernel flash if thats the order he did it in wouldn't it have? Im thinking it was a bad Cleanrom download he was trying to flash since it gave an error in recovery when he tried to flash it and wouldn't load it at all. Or maybe a bad TWRP image? Just guessing here.
Click to expand...
Click to collapse
I also tried installing multiple other ROMs, all giving me the same zip error in TWRP. I forgot to mention that before I installed CM10.1 I downloaded GooManager and that's what kept prompting me to install the CM10.1 version. I also installed the latest TWRP through GooManager as that was what was recommended in the TWRP post as the best way to do so.
afrat said:
I followed the instructions given in the Bulletproof-1.0 post that said to install the zip via TWRP. I did that and everything went fine.
Click to expand...
Click to collapse
If you keep reading on the Bulletproof instructions, you will see:
hboot 1.14+ and S-ON:
The installer includes a method to flash the boot.img for S-ON devices using hboot 1.14 or higher;
however, some people still have difficulties. If it doesn't work:
1. extract boot.img from the zip, reboot to bootloader and do:
fastboot flash boot boot.img
---------- Post added at 04:26 PM ---------- Previous post was at 04:21 PM ----------
eraste said:
In op it says he flashed kernel then rom, the rom would have overwritten the kernel flash if thats the order he did it in wouldn't it have?
Click to expand...
Click to collapse
With hboot<1.14, or with S-on yes. But in his case no. For hboot 1.14 and higher and S-on, you can flash the kernel before or after the ROM, it doesn't matter since the kernel can't be flashed from recovery.
---------- Post added at 04:29 PM ---------- Previous post was at 04:26 PM ----------
afrat said:
I also tried installing multiple other ROMs, all giving me the same zip error in TWRP. I forgot to mention that before I installed CM10.1 I downloaded GooManager and that's what kept prompting me to install the CM10.1 version. I also installed the latest TWRP through GooManager as that was what was recommended in the TWRP post as the best way to do so.
Click to expand...
Click to collapse
What version of TWRP? The latest build has some serious problems. zip errors for multiple ROMs is making me think its TWRP that is causing you the headache, for the most part.
redpoint73 said:
What version of TWRP? The latest build has some serious problems. zip errors for multiple ROMs is making me think its TWRP that is causing you the headache, for the most part.
Click to expand...
Click to collapse
I'm not sure. If I did the RUU, does that mean I lost the custom recovery (TWRP) that I've installed as well?
I just tried to install the 4.1 OTA update from AT&T. I donwloaded the update and proceeded to install it, but after it restarted everything on my phone was erased and it was set back to factory default on 4.0.1. Now when I check for updates it tells me there are nor updates, the server is full, or 'HtcDm has stopped'. What the hell happened there?
I went ahead and tried the OTA update again and now my phone won't turn on and shows no status LED light when plugged in. Back to Best Buy it goes. I need a Nexus...
afrat said:
I went ahead and tried the OTA update again and now my phone won't turn on and shows no status LED light when plugged in. Back to Best Buy it goes. I need a Nexus...
Click to expand...
Click to collapse
Ok. Wierd. You think the ota bricked your phone? It wont power on in any way? No recovery or anything?
Note 2 ftw
eraste said:
Ok. Wierd. You think the ota bricked your phone? It wont power on in any way? No recovery or anything?
Note 2 ftw
Click to expand...
Click to collapse
It's completely dead. It's quite alright though, Best Buy said they will replace it for me. Gotta love that insurance!
afrat said:
It's completely dead. It's quite alright though, Best Buy said they will replace it for me. Gotta love that insurance!
Click to expand...
Click to collapse
Thats good. But if this did cause the brick knowing what it was would help others! So you were completely stock on the 2.20 ruu then tried to install the OTA right?
Did you have supercid?
eraste said:
Thats good. But if this did cause the brick knowing what it was would help others! So you were completely stock on the 2.20 ruu then tried to install the OTA right?
Did you have supercid?
Click to expand...
Click to collapse
I was completely stock from the 2.20 RUU and then tried applying the OTA update. I started to OTA update once and it rebooted my phone a few times only to have it reset to factory settings with 4.0.4. I then checked multiple times by bumping my clock forward to get the update again (I am assuming the servers were busy which is what was giving me errors). I was able to get the update to download again and then began installing it for a second time. This time is sat on the screen with the refresh icon over the phone with the status bar underneath for a few minutes, then restarted three times with just the phone icon on it, and then powered off completely, never to turn on again.
I did have supercid, at least I think I did, I can't remember exactly what I did to obtain root/unlocked bootloader/custom roms back when I first started messing with it.
afrat said:
I was completely stock from the 2.20 RUU and then tried applying the OTA update. I started to OTA update once and it rebooted my phone a few times only to have it reset to factory settings with 4.0.4. I then checked multiple times by bumping my clock forward to get the update again (I am assuming the servers were busy which is what was giving me errors). I was able to get the update to download again and then began installing it for a second time. This time is sat on the screen with the refresh icon over the phone with the status bar underneath for a few minutes, then restarted three times with just the phone icon on it, and then powered off completely, never to turn on again.
I did have supercid, at least I think I did, I can't remember exactly what I did to obtain root/unlocked bootloader/custom roms back when I first started messing with it.
Click to expand...
Click to collapse
Strange. Really strange.
eraste said:
Strange. Really strange.
Click to expand...
Click to collapse
It is indeed. I am wondering if all my random flashing attempts at different kernels and boot.img files and ROMs just messed something up. I thought that doing the RUU replaced EVERYTHING I could have done to my phone, minus the unlocked bootloader, so maybe it was just a messed up OTA file.
Regardless, I am very glad I got the BB insurance plan. I can have my device completely replaced multiple times during the 2-year plan and there is no deductible or rate increase, it's crazy.
I seem to recall that some people who took the OTA with supercid on earlier JB updates reported getting bricked.
afrat said:
It is indeed. I am wondering if all my random flashing attempts at different kernels and boot.img files and ROMs just messed something up. I thought that doing the RUU replaced EVERYTHING I could have done to my phone, minus the unlocked bootloader, so maybe it was just a messed up OTA file.
Regardless, I am very glad I got the BB insurance plan. I can have my device completely replaced multiple times during the 2-year plan and there is no deductible or rate increase, it's crazy.
Click to expand...
Click to collapse
Yes ruu would have put you back to stock with the exception of supercid that would have stayed.
iElvis said:
I seem to recall that some people who took the OTA with supercid on earlier JB updates reported getting bricked.
Click to expand...
Click to collapse
Me to this was my initial thought super cid was the culprit!
eraste said:
Me too this was my initial thought super cid was the culprit!
Click to expand...
Click to collapse
But some others insisted that it couldn't have been the issue. SuperCID is supposed to allow flashing of any updates regardless of CID restrictions.
First let me say that I'm kinda new to android flashing and I'm learning, so please be understanding.
A few days ago I got in my hands an i9003 and decided to root and unlock it, I thought I had made an /efs backup, but, as a matter of fact this backup turned out to be empty, as apparently I didn't backup with root permision. A day later decided to install CM11 and I followed this tutorial: bit.ly/J5d5UL When I tried to install the ROM it rebooted and it got stuck in recovery mode. I read extensively over what to do, so I decided to flash back to stock (UBKB1, as I'm from Argentina and this is the Latin american Froyo stock). I've had no luck with this: it is now stuck with the glowing Samsung logo right after the boot animation. I've read that the CF-Root used in the tutorial, amit.bagaria one, it's intended to work with Gingerbread, and I had Froyo installed when I started the tutorial, ¿can this be the cause of everything? ¿Is there something I can do? I've also read to flash to KPE first and then on to others, but I'm worried that, as I don't have my /efs backup, I could lose my 3g and/or IMEI.
Thanks in advance, and also I apologize any grammar errors I could have as English isn't my native language.
sjvega said:
First let me say that I'm kinda new to android flashing and I'm learning, so please be understanding.
A few days ago I got in my hands an i9003 and decided to root and unlock it, I thought I had made an /efs backup, but, as a matter of fact this backup turned out to be empty, as apparently I didn't backup with root permision. A day later decided to install CM11 and I followed this tutorial: bit.ly/J5d5UL When I tried to install the ROM it rebooted and it got stuck in recovery mode. I read extensively over what to do, so I decided to flash back to stock (UBKB1, as I'm from Argentina and this is the Latin american Froyo stock). I've had no luck with this: it is now stuck with the glowing Samsung logo right after the boot animation. I've read that the CF-Root used in the tutorial, amit.bagaria one, it's intended to work with Gingerbread, and I had Froyo installed when I started the tutorial, ¿can this be the cause of everything? ¿Is there something I can do? I've also read to flash to KPE first and then on to others, but I'm worried that, as I don't have my /efs backup, I could lose my 3g and/or IMEI.
Thanks in advance, and also I apologize any grammar errors I could have as English isn't my native language.
Click to expand...
Click to collapse
sometimes while installing rom the phone automatically reboots into recovery.. but tht is normal.. then u have to again flash the rom ... but for now .. try clearing dalvik cache in recovery mode... and reboot .. if tht doesnt work then using odin flash back to kpe .. here is a video link http://m.youtube.com/watch?v=2crS2rZgUQc&desktop_uri=/watch?v=2crS2rZgUQc and u can loose ur internal data so backup...
hit thanks if i helped
Thanks for the reply.
Sorry I didn't specify further, when it was booting continuously into recovery I tried to install the ROM, but it threw an error (#7 if I recall correctly) and then it kept looping into recovery.
I'll try to flash CWM now (as I don't have it flashed after flashing stock) and do the wipes.
EDIT: I've flashed CWM for the firm I had installed, wiped everything, reflashed and it still doesn't work, I'd like to avoid KPE until I'm sure I can recover the /efs folder as I don't want lo lose connectivity of any sort. Update: during wiping CWM said it can't mount /datadata
Thanks anyway
Last Update:I've got a KPE for my region so I've flashed it, I've also flashed amit.bagaria's universal CWM, it kept looping, so I tried to install the rom, unsuccessfully, it reboots on a different version of CWM, and if I try to install it again it says:
Installing update...
"assert failed: run_program("/tmp/updater.sh")==0
E:Error in /storage/sdcard1/cm-11-20131209-UNOFFICIAL-galaxysl.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
sjvega said:
Thanks for the reply.
Sorry I didn't specify further, when it was booting continuously into recovery I tried to install the ROM, but it threw an error (#7 if I recall correctly) and then it kept looping into recovery.
I'll try to flash CWM now (as I don't have it flashed after flashing stock) and do the wipes.
EDIT: I've flashed CWM for the firm I had installed, wiped everything, reflashed and it still doesn't work, I'd like to avoid KPE until I'm sure I can recover the /efs folder as I don't want lo lose connectivity of any sort. Update: during wiping CWM said it can't mount /datadata
Thanks anyway
Last Update:I've got a KPE for my region so I've flashed it, I've also flashed amit.bagaria's universal CWM, it kept looping, so I tried to install the rom, unsuccessfully, it reboots on a different version of CWM, and if I try to install it again it says:
Click to expand...
Click to collapse
leave amit bagaria zip aside... flash this on kpe using odin link:- http://www.mediafire.com/download/vh701fh312la2v9/ZHKPE-CFROOT-25-05-2012.tar . after odin detects your device. go to PDA option and select this zip file from your computer and flash.. this will root your device and add a cwm recovery. and let me know what happened.. and even iam not a professional. but i were u i would have tried all possible ways.. have fun.. we ill get a way out of it..
hit thanx if i helped
Excuse me but, ¿PIT? ¿isn't it PDA? Also, that CWM isn't for the firm of the region I have, ¿wouldn't I have problems flashing that one?
I've been reading that it could be that the internal memory is corrupted, ¿is there a way to check this?
sjvega said:
I've been reading that it could be that the internal memory is corrupted, ¿is there a way to check this?
Click to expand...
Click to collapse
sorry bro ! its pda .. i havent used odin for months so.... and iam not sure region would cause any problem ! it will be better to consult a professional.... and even ill read about it and post if i get something..
Ok, so I kept reading about it and it doesn't seem to be a corrupted memory, there are some errors that should appear and they don't.
I've been recomended to flash to XXKB3 as it doesn't modify the IMEI file, and then if that doesn't work flash XXKPE; I'm having a hard time finding it though, as all hotfile links are dead.
Ok! I've flashed XXKP3 and finally it booted. I'll see to take other problems I might have somewhere else.
Hey guys, just looking for some help with this. For the record, I was using TWRP 2.8. Last night I tried to install NuSenseSIX from the development forum, only to have this error: set_perm: some changes failed. Thinking it was just a problem with the download, I downloaded a second copy, checked the MD5 (which was the same), flashed it, same error. I then tried flashing DigitalHigh's GPE Rom, but the same error had came up. I RUU'd the phone back to stock (credit for the RUU goes to dottat), installed TWRP, flashed:failed. Flashed CWM, Rom flash:failed (every Rom I mentioned before failed to flash). Everything had the same error, although CWM reported it as Error 7. The only Rom that installs successfully and boots is CM11, I have no clue as to why. I'm stuck, I don't know what to do. Any help would be greatly appreciated.
EDIT: Only the CM11 M10 Snapshot will flash, I just tried to flash the latest nightly (10/5/14) and it gave me "assert failed: run program("/system/bin/makelinks.sh") == 0"
RealROGWaffle said:
Hey guys, just looking for some help with this. For the record, I was using TWRP 2.8. Last night I tried to install NuSenseSIX from the development forum, only to have this error: set_perm: some changes failed. Thinking it was just a problem with the download, I downloaded a second copy, checked the MD5 (which was the same), flashed it, same error. I then tried flashing DigitalHigh's GPE Rom, but the same error had came up. I RUU'd the phone back to stock, installed TWRP, flashed:failed. Flashed CWM, Rom flash:failed (every Rom I mentioned before failed to flash). Everything had the same error, although CWM reported it as Error 7. The only Rom that installs successfully and boots is CM11, I have no clue as to why. I'm stuck, I don't know what to do. Any help would be greatly appreciated.
EDIT: Only the CM11 M10 Snapshot will flash, I just tried to flash the latest nightly (10/5/14) and it gave me "assert failed: run program("/system/bin/makelinks.sh") == 0"
Click to expand...
Click to collapse
Try doing another ruu. Then boot to hboot and chose factory reset. Make sure you do not flash twrp before doing the factory reset.
dottat said:
Try doing another ruu. Then boot to hboot and chose factory reset. Make sure you do not flash twrp before doing the factory reset.
Click to expand...
Click to collapse
Hey dottat! Sorry I forgot to give you credit for the ruu. I'll give that a shot after work tomorrow. Thanks for the reply. By the way, what does flashing TWRP before doing the factory reset do? I flashed mine without even doing that.
RealROGWaffle said:
Hey dottat! Sorry I forgot to give you credit for the ruu. I'll give that a shot after work tomorrow. Thanks for the reply. By the way, what does flashing TWRP before doing the factory reset do? I flashed mine without even doing that.
Click to expand...
Click to collapse
Factory reset using stock recovery can fix things twrp sometimes can't.
dottat said:
Factory reset using stock recovery can fix things twrp sometimes can't.
Click to expand...
Click to collapse
Alright, thanks. As I said, I'll try it tomorrow. I'll report back with new info.
By the way, what's the difference between the old ruu you made and the new one? I flashed the old one and I want to know if that might be why it didn't fix my issue.
Well... same issue after doing what you said. I'm honestly really sad right now.
RealROGWaffle said:
Well... same issue after doing what you said. I'm honestly really sad right now.
Click to expand...
Click to collapse
I have one more thing I'm going to pm you to try.