I recently changed back my build.prop to the original one that i backed up before. Then my device cannot boot anymore. It is stuck in the ASUS splash screen when i boot the device.
Then I flash the latest CWM recovery. But even the latest version it cannot do anything like factory reset or flash zip.
After that, i tried to use the "wipe data" in the bootloader, it doesn't work either (still stuck in the splash screen).
And then i tried cold boot linux and it also doesn't work. Up to this point, I cannot find anyway to fix it.
However, I found that adb is somewhat working in CWM recovery. I tried "adb push build.prop /system/build.prop" (the build.prop is extracted from the US_epaduser_10_26_1_7_UpdateLauncher.zip package from ASUS official site), it doesn't work either.
I put the US_epaduser_10_26_1_7_UpdateLauncher.zip package from asus support site in sd card and tried to flash it by CWM recovery, it doesn't work either.
AFTER ALL THESE PROCEDURE, i think the system is corrupted because of some possible dirty wipe
IS THERE ANY WAY TO WIPE EVERYTHING AND RESET THE whOLE SYSTEM?
i feel like my device is completely dead... so i need help and solution asap
my device is unlocked, rooted, and updated to 10.26.1.7 android 4.3.
it is a US version.
btw i asked ASUS support and they said they would charge CAN$330 for fixing it (replacing the main board), which is.........
bruce2662 said:
I recently changed back my build.prop to the original one that i backed up before. Then my device cannot boot anymore. It is stuck in the ASUS splash screen when i boot the device.
Then I flash the latest CWM recovery. But even the latest version it cannot do anything like factory reset or flash zip.
After that, i tried to use the "wipe data" in the bootloader, it doesn't work either (still stuck in the splash screen).
And then i tried cold boot linux and it also doesn't work. Up to this point, I cannot find anyway to fix it.
However, I found that adb is somewhat working in CWM recovery. I tried "adb push build.prop /system/build.prop" (the build.prop is extracted from the US_epaduser_10_26_1_7_UpdateLauncher.zip package from ASUS official site), it doesn't work either.
I put the US_epaduser_10_26_1_7_UpdateLauncher.zip package from asus support site in sd card and tried to flash it by CWM recovery, it doesn't work either.
AFTER ALL THESE PROCEDURE, i think the system is corrupted because of some possible dirty wipe
IS THERE ANY WAY TO WIPE EVERYTHING AND RESET THE whOLE SYSTEM?
i feel like my device is completely dead... so i need help and solution asap
my device is unlocked, rooted, and updated to 10.26.1.7 android 4.3.
it is a US version.
btw i asked ASUS support and they said they would charge CAN$330 for fixing it (replacing the main board), which is.........
Click to expand...
Click to collapse
Since it seems that cwm works did you make nandroid backup before you started fiddling with the Rom? ( basic rule nr.1)
When not go to the boot loader screen and do a factory reset there (third icon from left).
But maybe you can do that also from within cwm but I do not know if it is in there.
The official update zip you must unzip that first and then put the new zip on the sdcard, can't do that from cwm.
Let it reboot and it must start flashing.
Snah001 said:
Since it seems that cwm works did you make nandroid backup before you started fiddling with the Rom? ( basic rule nr.1)
When not go to the boot loader screen and do a factory reset there (third icon from left).
But maybe you can do that also from within cwm but I do not know if it is in there.
The official update zip you must unzip that first and then put the new zip on the sdcard, can't do that from cwm.
Let it reboot and it must start flashing.
Click to expand...
Click to collapse
So is there any ways to fix it without sending it to asus repair ccenter?
I want to make sure that
1. The wipe data function in the bootloader works
2. Does wiping data in bootloader fix the build.prop problem
Or do anyone of you have any idea of solving tthis problem?
sorry for my bad english
bruce2662 said:
So is there any ways to fix it without sending it to asus repair ccenter?
I want to make sure that
1. The wipe data function in the bootloader works
2. Does wiping data in bootloader fix the build.prop problem
Or do anyone of you have any idea of solving tthis problem?
sorry for my bad english
Click to expand...
Click to collapse
Wipe data is like factory reset.
Unzip the firmware package and put the zip on your microSD. Then reboot and let it flash.
This way you get all a clean fresh install
Snah001 said:
Wipe data is like factory reset.
Click to expand...
Click to collapse
Sorry to disagree..
I would NOT wipe from the bootloader with a custom recovery installed! People have hard bricked their tablets that way!
Unzip the firmware package and put the zip on your microSD. Then reboot and let it flash.
This way you get all a clean fresh install
Click to expand...
Click to collapse
That works only with the stock recovery, not with a custom recovery. But you should be able to flash the once unzipped firmware in CWM. That would flash you back to stock, including the stock recovery.
Next time you install CWM your first action should be to make a nandroid.
If it doesn't work please explain why and what. Just "doesn't work" is not helpful - do you get error messages?
Explain - in detail - your steps.
Since you said you flashed CWM you do have fastboot access?
Forgot that you aren't on stock recovery.
When you still get into the recovery did you unzip the factory firmware zip before you tried to flash it?
First give that a try.
Volume-up + power pressed normally would get you into apx mode but since we have no Nvflash files available you can't do anything with that.
So unpack and put the factory firmware zip on you sdcard and flash from custom (think you have cwm installed) recovery (choose install and choose the file you put on your microSdcard).
Del msg
Hi I got an issue today with my TF701T can anyone help.
I got a prompt for installing an update, downloaded it, installed and on reboot the TF701T is stuck on the ASUS Splash screen.
How do you reset this device? I'm new to this TF701T
ToneyEricsson said:
Hi I got an issue today with my TF701T can anyone help.
I got a prompt for installing an update, downloaded it, installed and on reboot the TF701T is stuck on the ASUS Splash screen.
How do you reset this device? I'm new to this TF701T
Click to expand...
Click to collapse
There are a number of users with the same issue. Asus seems to have pushed an incompatible update to WW users (Man! They are really scre*** the release of this device! Unbelievable...)
Head over to the General section, there are a couple of threads dealing with this issue. The fix seems to be to wipe data and manually re-install the 10.26.1.7. (and ignore the update notifications you'll get again!)
But read the threads before you do so...
berndblb said:
There are a number of users with the same issue. Asus seems to have pushed an incompatible update to WW users (Man! They are really scre*** the release of this device! Unbelievable...)
Head over to the General section, there are a couple of threads dealing with this issue. The fix seems to be to wipe data and manually re-install the 10.26.1.7. (and ignore the update notifications you'll get again!)
But read the threads before you do so...
Click to expand...
Click to collapse
Sure buddy I will be reading xda before installing any updates from now on!!! Thats really bad ASUS pushed this update out that gets owners of the TF701T stuck on the Splash Screen after updating.
ToneyEricsson said:
Sure buddy I will be reading xda before installing any updates from now on!!! Thats really bad ASUS pushed this update out that gets owners of the TF701T stuck on the Splash Screen after updating.
Click to expand...
Click to collapse
Haha funny :cyclops:, same problem for the UK devices too (i see you´re from London?)? OMG!
I´m a german user and a bunch of peopole here also had this kind of issue after they did the last update from 4.3 to any newer release, since 27th dezember 2013 there´s no valid reply from ASUS and (for my understanding) the invalid software update is still on the servers and get sent to the EU users (...).
@ XDA: do you know, where i could find out the local storage where on my device the *.zip (or what ever) is saved, so that i could manually delete it? To make sure i´ll receive a newer one in future? Or did this (incorrect 250,8MB file) will be replaced by the newer one?
Regards
Silver
Try the root of your internal sdcard or in the download folder.
Sent from my Asus Infinity TF700 with Dock
where can i delete this file
Hi guys,
i've got the same issue, sent the device to the service and replaced a part of it, but because they've went over the 15 days period where they should have send it back ( fixed or not) I got a new one.
i updated to 4.3 and this time again i got prompted to install the crap update, but i didn't. Now i want to delete this file but i can't find it. if my kid or someone else will accidentally say OK to the update i'm back to older version ( at the best) .
so will be highly appreciated if anybody will provide a solution to remove this file.
thx
Snah001 said:
Try the root of your internal sdcard or in the download folder.
Sent from my Asus Infinity TF700 with Dock
Click to expand...
Click to collapse
xistentz said:
Hi guys,
i've got the same issue, sent the device to the service and replaced a part of it, but because they've went over the 15 days period where they should have send it back ( fixed or not) I got a new one.
i updated to 4.3 and this time again i got prompted to install the crap update, but i didn't. Now i want to delete this file but i can't find it. if my kid or someone else will accidentally say OK to the update i'm back to older version ( at the best) .
so will be highly appreciated if anybody will provide a solution to remove this file.
thx
Click to expand...
Click to collapse
It'll be on the cache partition, which you can only access from the stock recovery - you'll need to boot to nthe boot loader, choose rck and mess around with power and volume up / down until the menu appears. Then choose wipe cache. But it will come back when you next check for an update......
Related
Please read this post in its entirety before downloading and flashing.
THIS IS FOR I9020T ONLY! IF YOU DECIDE TO GET BRAVE AND TRY THIS ON AN I9020A, I9023 OR D720, MAY THE FORCE BE WITH YOU. I AM NOT RESPONSIBLE FOR ANY DAMAGE CAUSED TO ANY PHONE BY USING THIS ROM.
YOU MUST FLASH THIS ROM USING CLOCKWORKMOD RECOVERY. THIS WILL NOT FLASH USING THE STOCK ANDROID 3E RECOVERY AS THE ZIP FILE IS NOT SIGNED. I HAVE NOT TESTED IT ON OTHER RECOVERIES.
This is probably more for posterity now than anything else, however I have created a CWM-flashable full on ROM for the Nexus S Gingerbread firmware, version 2.3.2, build GRH78C. This is built exactly the same way that the full OTA ROM packages for 2.3.3 and 2.3.4 were built.
Some notes:
1. Flashing this ZIP will remove ClockworkMod Recovery on first boot. Android 2.3.2 contains a script that automatically overwrites alternate recoveries with the stock Android 3e recovery each time you reboot your phone. The script is located in /system/etc/install-recovery.sh. If you root the ROM, you can rename this file to avoid flashing the stock recovery on each reboot.
2. Flashing this ZIP will overwrite your bootloader and radio, restoring them to I9020XXJK1 and I9020XXJK8 respectively. These are the versions that came stock with GRH78C.
3. GRH78C is receiving OTA updates. As of this writing, the latest version of Android is 2.3.4, and Google is pushing an OTA update for 2.3.2 to 2.3.4.
4. This ZIP will NOT clear your user data or cache. For users running a stock ROM, I would highly suggest clearing your data and cache manually as sometimes downgrading without clearing data and cache can cause problems. If you are coming from a non-stock ROM, you are required to clear your data and cache or the ROM will not boot.
5. Since writing NFC tags wasn't introduced until GRI40/2.3.3, the Tags app is read-only.
6. There is no video chatting through Google Talk. This feature was not introduced until GRJ22/2.3.4.
Instructions:
1. Download the Stock GRH78C ROM package here.
2. Copy it to the root of your USB storage.
3. Reboot into ClockworkMod Recovery (or flash it).
4. Select "Install ZIP From SD Card"
5. Select "Choose ZIP"
6. Find the ZIP file and select it.
7. Wait for it to finish.
8. Wipe data and cache (optional but HIGHLY recommended for stock ROM users and REQUIRED for non-stock ROM users)
9. Reboot and have fun.
Reserved...just in case.
Thank You will post results if needed,i doubt it,again thank you very much,ping33tx
I can access the bootloader, I can access the clockwordrecovery, odin recognizes the device, but I can not access the intern sd.
I can only try to restore by odin
I'm looking rom to use the odin.
My nexus s is bricked, anyone help-me
I'm Brazilian and I used google translate, sorry.
i was googling for stock roms and found this
i had no idea if i have the i9020t or not
now my phone wont even turn on, no life
any ideas?
*EDITED: not sure which version i do have actually
SS2006 said:
this rom was bad...i was googling for stock roms and found this
i have the i9020t
now my phone wont even turn on, no life
any ideas?
Click to expand...
Click to collapse
Wanted to flash this ROM, just wanted you to confirm that yours is an i9020A, not i9020T, therefore that's the reason why it won't turn on now.
Sorry for your phone by the way.
that could be the reason, i got this phone for very cheap and it was soft bricked so i had no idea if it was 9020a or 9020t (no box with it)
if this is the case, what can i do, USB jig or jtag?
Can you boot it to bootloader?
From off position, try Vol UP + Power.
If you can see the Android logo and 4 menu options, you got yourself a great deal.
SS2006 said:
that could be the reason, i got this phone for very cheap and it was soft bricked so i had no idea if it was 9020a or 9020t (no box with it)
if this is the case, what can i do, USB jig or jtag?
Click to expand...
Click to collapse
See at the back of your battery....
reboot to boatloader..
hopefully you can still get to recovery...
al_madd said:
See at the back of your battery....
reboot to boatloader..
hopefully you can still get to recovery...
Click to expand...
Click to collapse
He doesn't need to. If he can get to the bootloader, he can flash and boot a recovery via fastboot.
No guys, seems i got myself in a mess. It is indeed a i9020a (the info under battery was erased so i didnt know0 and i flashed the i9020t rom in this thread (different radios)
so this thing is HARD bricked, screen won't turn on, no bootloader, nothing, tried to get it into download mode (even without screen turning on) assuming it was working, but odin doesn't realize its there
so i think my only solution is jtag. I can buy a usb jig but I think that usb jigs dont do anything for hard bricked phones, am i right
Much thanks for your help.
Hi there,
Not long ago i got a P970 and proceeded to root it and install CWM on my device using an all in one solution from this site, unfortunately it didn't seem to create a backup of the stock bootloader and i am unable to perform updates to the device as they all try to boot in to the stock bootloader to finish the update process which is ofc missing, does anyone have a copy of the stock bootloader for the P970, incase its of relevance i'm using one in the UK on the Orange network
I thank you in advance for any replies
Bump anyone got a copy of the bootloader?
If you flash stock vanilla rom it will overwrite CWM with stock.
dflt said:
If you flash stock vanilla rom it will overwrite CWM with stock.
Click to expand...
Click to collapse
Couple of small issues is that i dont want to lose everything i've installed and setup so far and the only images i can find of the stock ROM's are .kdz files which use the LG tools to flash and those require me to be able to boot to the standard software update tool found on the phone which doesn't seem to work with CWM installed as i can't do any OTA updates either.
dude, I already answered to you by pm. this cannot be saved, you have to flash again to recover the standard loader. AND, you don't have to boot or something else except going in s/w mode. just backup your apps / datas with 3nd party app then restore them after the flash. standard recovery is absolutely uneeded and is even useless. you might restore full datas with cwm by going into the advanced menu.
Hi, device is rooted, and clockworkmod recovery 6.0.4.5 installed.
ROM is JB, the official update from LG. Today device reported there is an update to the installed firmware.
I rebooted in CM recovery, took a nandroid backup, booted, and accepted to download the official update to my official JB rom. After downloading I was asked to reboot (in order to install), and the phone reboots to the CM recovery.
From there I don't know what to do. I have tried rebooting, but again find myself to the CM recovery. I have tried "reboot to bootloader" and get stuck at the LG boot screen logo with the message "Now Ready!" in tiny white letters on the upper left corner.
I would try "install zip" but I don't know where the downloaded update is (if it even is in an acceptable zip format)
Phone isn't bricked, I guess I can always restore from the recently taken backup, but I really would like to know if there is a way to install this update.
Thank you
http://forum.xda-developers.com/showthread.php?p=50645445
Could you please please please try to search the next time I've seen this question for probably 3-4 times
Sent from my LG-P880 using xda app-developers app
you can't ota over unlocked bl/cwm, you must flash update manually
moneyvirus said:
http://forum.xda-developers.com/showthread.php?p=50645445
Could you please please please try to search the next time I've seen this question for probably 3-4 times
Click to expand...
Click to collapse
You're right, but you know, sometimes you just can't nail the right keywords especially if its not your native language. I searched, but obviously not good enough.
Rudjgaard said:
you can't ota over unlocked bl/cwm, you must flash update manually
Click to expand...
Click to collapse
Sadly, this seems to be the case.. bummer.
Thanks everyone
Not even my nandroid backup can help me get to where I was before? So much for nandroid being the ultimate backup, a "snapshot image" of the device...
So, what if, I use CM recovery to install a custom rom, and then restore from my nandroid backup (being the official JB) ?
Flash with kdz flasher original ROM then flash cwm you can put back your backup. I think the problem starts that the update pushes something in the boot section that is expecting an other (read original) recovery . when you installed cwm it boots up cwm so that's why an nandroid backup doesn't work I think ( to be honest I'm not 100% sure this is correct)
Sent from my LG-P880 using xda app-developers app
I can't even flash cyanogenmod???
I downloaded latest stable build, copied it to sd card, selected it from the CM recovery ("install zip"), installed fine, reboot, still stuck at CM recovery!!!
What gives?
EPa said:
I can't even flash cyanogenmod???
I downloaded latest stable build, copied it to sd card, selected it from the CM recovery ("install zip"), installed fine, reboot, still stuck at CM recovery!!!
What gives?
Click to expand...
Click to collapse
Have you yet followed the advice and installed the KDZ?
Trying to avoid that, as it seems too much work for a phone that was working fine, and stuck to recovery due to some silly boot flag or something.
Saw it as a chance to try cyanogenmod. But it seems having CM recovery and the cyanogenmod rom on the sd card won't cut it! Talk about failure..
EPa said:
Trying to avoid that, as it seems too much work for a phone that was working fine, and stuck to recovery due to some silly boot flag or something.
Saw it as a chance to try cyanogenmod. But it seems having CM recovery and the cyanogenmod rom on the sd card won't cut it! Talk about failure..
Click to expand...
Click to collapse
I don't think you will have a choice. If you created the nandroid backup on your SD card then you aren't going to lose it, so just flash the KDZ, root again and install your backup, or accept the LG update and rebuild all your software again.
Yes, one thing is for sure. I had to install the KDZ to be able to proceed with anything..
It's just funny having a working CWM recovery and a cyanogen rom on the device and after flashing it, still not having a device that boots. A "recovery"/flash tool, should be able to "recover" from such a situation..
EPa said:
Yes, one thing is for sure. I had to install the KDZ to be able to proceed with anything..
It's just funny having a working CWM recovery and a cyanogen rom on the device and after flashing it, still not having a device that boots. A "recovery"/flash tool, should be able to "recover" from such a situation..
Click to expand...
Click to collapse
You can't blame the recovery. It is clearly stated many, many times that you should never attempt an official OTA update with a non-standard (rooted or recovery installed) device. On other devices you could even hard-brick AFAIK, so consider yourself lucky that you only had to reflash a KDZ and start again.
For restoring stock rom use this: http://forum.xda-developers.com/showthread.php?t=2682146 I can confirm it works and it is (very) easy.
Yes that's what I used and I also confirm it works and is very easy.
My i9305 LTE is caught in a boot loop (just loops the start-up screen of any ROM I install). I have access to CWM recovery v6.0.4.5 and also download recovery.
The only thing I can think that might have caused this was when I installed Archidroid I (foolishly?) selected the only partition that wasn't ext4, to be set as ext4. It's not booted past any of the bootscreens on any ROM since I did this.
I've tried wiping all data and cache and also doing a data/factory reset and every "clear data" option available and I'm still caught in a boot screen loop on any ROM I try.
I've formatted each of the folders on the device by mounting and formatting (I don't need to keep any data on the phone) and then to get a new ROM on the phone I've inserted an SD Card, mounted it in CWM recovery and installed it from the .zip that way, all ROMs I've tried just lock up at their boot screen, it just loops over and over.
I've searched this forum and on Google but cannot find a solution or anyone with a similar issue, most that have had a similar looping problem say they performed an Odin factory reset, which brings me to my next question.
I don't know the region of my phone as I cannot access the dialler or any of my settings to find out the region, and forgot (as I rooted so long ago). I do have on the back of the phone the codes:
FCC ID: A3LGI9305
SSN: -I9305GSMH
as well as my IMEI #
How do I know my phone region, and which firmware/rom would I use to perform a full factory reset to at least get it booting again?
Any tips/ideas please, that would be much appreciated.
likeasir said:
My i9305 LTE is caught in a boot loop (just loops the start-up screen of any ROM I install). I have access to CWM recovery v6.0.4.5 and also download recovery.
The only thing I can think that might have caused this was when I installed Archidroid I (foolishly?) selected the only partition that wasn't ext4, to be set as ext4. It's not booted past any of the bootscreens on any ROM since I did this.
I've tried wiping all data and cache and also doing a data/factory reset and every "clear data" option available and I'm still caught in a boot screen loop on any ROM I try.
I've formatted each of the folders on the device by mounting and formatting (I don't need to keep any data on the phone) and then to get a new ROM on the phone I've inserted an SD Card, mounted it in CWM recovery and installed it from the .zip that way, all ROMs I've tried just lock up at their boot screen, it just loops over and over.
I've searched this forum and on Google but cannot find a solution or anyone with a similar issue, most that have had a similar looping problem say they performed an Odin factory reset, which brings me to my next question.
I don't know the region of my phone as I cannot access the dialler or any of my settings to find out the region, and forgot (as I rooted so long ago). I do have on the back of the phone the codes:
FCC ID: A3LGI9305
SSN: -I9305GSMH
as well as my IMEI #
How do I know my phone region, and which firmware/rom would I use to perform a full factory reset to at least get it booting again?
Any tips/ideas please, that would be much appreciated.
Click to expand...
Click to collapse
what country do you live? the region is the country you live in, just search for your official firmware on sammobile or samsung update site. and download the firmware for your country, flash it with odin.
also update your recovery to the latest available in your case cwm 6.0.4.7
PHP:
MaHo_66 said:
what country do you live? the region is the country you live in, just search for your official firmware on sammobile or samsung update site. and download the firmware for your country, flash it with odin.
also update your recovery to the latest available in your case cwm 6.0.4.7
Click to expand...
Click to collapse
I live in Australia but am slightly worried as I bought my phone from Koga online so it's an internationally shipped phone I think originally intended for the uk as it had a uk adaptor for the plug does this matter?
likeasir said:
PHP:
I live in Australia but am slightly worried as I bought my phone from Koga online so it's an internationally shipped phone I think originally intended for the uk as it had a uk adaptor for the plug does this matter?
Click to expand...
Click to collapse
Hmm... Good question. I understand your issue here but im afraid i cant answer this.. While it was working what firmware was running on it? What baseband? If you have any kind of info of the working firmware, analyze it with firmwares on those sites and try to find the one you need.
Sent from my GT-I9305 using XDA Premium 4 mobile app
likeasir said:
My i9305 LTE is caught in a boot loop (just loops the start-up screen of any ROM I install). I have access to CWM recovery v6.0.4.5 and also download recovery.
The only thing I can think that might have caused this was when I installed Archidroid I (foolishly?) selected the only partition that wasn't ext4, to be set as ext4. It's not booted past any of the bootscreens on any ROM since I did this.
I've tried wiping all data and cache and also doing a data/factory reset and every "clear data" option available and I'm still caught in a boot screen loop on any ROM I try.
I've formatted each of the folders on the device by mounting and formatting (I don't need to keep any data on the phone) and then to get a new ROM on the phone I've inserted an SD Card, mounted it in CWM recovery and installed it from the .zip that way, all ROMs I've tried just lock up at their boot screen, it just loops over and over.
I've searched this forum and on Google but cannot find a solution or anyone with a similar issue, most that have had a similar looping problem say they performed an Odin factory reset, which brings me to my next question.
I don't know the region of my phone as I cannot access the dialler or any of my settings to find out the region, and forgot (as I rooted so long ago). I do have on the back of the phone the codes:
FCC ID: A3LGI9305
SSN: -I9305GSMH
as well as my IMEI #
How do I know my phone region, and which firmware/rom would I use to perform a full factory reset to at least get it booting again?
Any tips/ideas please, that would be much appreciated.
Click to expand...
Click to collapse
Well I was in the same pickle
whicever 4.3 rom i flashed through odin i got stuck in boot logo or even if i recovered device from odin through emergency frimware and intillation
Also tried customs 4.3 roms stuck a boot logo
Here what u should try and what i did
1 flash philz recovery + 4.1.2 rom
if it works back up efs
2 Using Philz recovery wipe data factory reset + wipe cache + dalvik cache
3 in mount and storage section format everything ( THINK THIS IS THE MOST IMPORTANT STEP )
4 Used odin to flash a 4.3 stock package it worked ( note u may get knox from this u may try a modifed stock package if u dont have knox and dont want to get it )
AMoizK said:
Well I was in the same pickle
whicever 4.3 rom i flashed through odin i got stuck in boot logo or even if i recovered device from odin through emergency frimware and intillation
Also tried customs 4.3 roms stuck a boot logo
Here what u should try and what i did
1 flash philz recovery + 4.1.2 rom
if it works back up efs
2 Using Philz recovery wipe data factory reset + wipe cache + dalvik cache
3 in mount and storage section format everything ( THINK THIS IS THE MOST IMPORTANT STEP )
4 Used odin to flash a 4.3 stock package it worked ( note u may get knox from this u may try a modifed stock package if u dont have knox and dont want to get it )
Click to expand...
Click to collapse
Thanks for your suggestion, I'll give that a shot tonight. I'm able to get into CWM as explained, mount and format everything so I'm not sure that this step will make a difference, but I'll do it again anyway.
So I'll see how it goes tonight. Actually been quite refreshing without a phone these past couple of days
likeasir said:
Thanks for your suggestion, I'll give that a shot tonight. I'm able to get into CWM as explained, mount and format everything so I'm not sure that this step will make a difference, but I'll do it again anyway.
So I'll see how it goes tonight. Actually been quite refreshing without a phone these past couple of days
Click to expand...
Click to collapse
I managed to fix it, but it had me totally stumped for a while.
I flashed philz recovery and then formatted all of the directories as I'd done previously on CWM.
I tried Slim Rom which didn't work.
I ended up tying CyanogenMod stable which actually worked, it got past the boot loop phase! - I was glad to see a setup screen after 2 days!
I then had another issue with my Cell Reception not working, no data or reception would be shown.
This seemed to happen since I tried a KitKat ROM, as I remember before the bootloop it did this on a couple of ROMs I tried to manually enter the APN over and over and it wouldn't let me save it, very annoying.
I checked the baseband in the about phone section and it was being displayed as "unknown", luckily I remembered my baseband # from when I rooted the phone about 8 months ago (XXBLL3), then I found on this forum a list of 9305i baseband downloads as .zips so I was able to load up CWM and flash it, reboot and it worked!
I will be keeping with CM Stable (10.1.3) for a while now.
I hope this helps someone else that might run into a similar issue.
likeasir said:
I managed to fix it, but it had me totally stumped for a while.
I flashed philz recovery and then formatted all of the directories as I'd done previously on CWM.
I tried Slim Rom which didn't work.
I ended up tying CyanogenMod stable which actually worked, it got past the boot loop phase! - I was glad to see a setup screen after 2 days!
I then had another issue with my Cell Reception not working, no data or reception would be shown.
This seemed to happen since I tried a KitKat ROM, as I remember before the bootloop it did this on a couple of ROMs I tried to manually enter the APN over and over and it wouldn't let me save it, very annoying.
I checked the baseband in the about phone section and it was being displayed as "unknown", luckily I remembered my baseband # from when I rooted the phone about 8 months ago (XXBLL3), then I found on this forum a list of 9305i baseband downloads as .zips so I was able to load up CWM and flash it, reboot and it worked!
I will be keeping with CM Stable (10.1.3) for a while now.
I hope this helps someone else that might run into a similar issue.
Click to expand...
Click to collapse
Cheers on getting ur phone fixed but after wiping all directories a stock rom flash would have cleared all the problems
lol i just did this to my phone, time to find a stock firmware.
So the case was I reset my device, and later after i flashed a ROM into my device, it does not boot. Instead, it goes into TWRP recovery. And it goes to TWRP every time i boot my device.
I have done this for so many times and I cannot even know what is going wrong this time. I am quite frustrated and I did googled a lot but it did not solve my problem. So, I want to know if anyone else encounter similar problem and solution towards it.
I tried:
1. Wipe the dalvik cache.
2. Remove the battery for half an hour
3. Reflash the twrp
Any efforts and reply is much appreciated.
Thank you.
Mine's exactly the same, I factory reset so I could pass the phone on; and now it will not install custom roms, I've tried about 7 or 8, and it will only boot into twrp 3.0.2-5. Soft brick, but I'm unable to find any solution.
Here's hoping someone will come and help.
I think I'll have to reinstall twrp by connecting the phone to the computer, but I've no idea how to do this.
slifer225 said:
So the case was I reset my device, and later after i flashed a ROM into my device, it does not boot. Instead, it goes into TWRP recovery. And it goes to TWRP every time i boot my device.
I have done this for so many times and I cannot even know what is going wrong this time. I am quite frustrated and I did googled a lot but it did not solve my problem. So, I want to know if anyone else encounter similar problem and solution towards it.
I tried:
1. Wipe the dalvik cache.
2. Remove the battery for half an hour
3. Reflash the twrp
Any efforts and reply is much appreciated.
Thank you.
Click to expand...
Click to collapse
Exactly the same issue here too, installed lineage 14.1, was working great, I was selling to a friend, did a factory reset, now stuck at twrp, roms install etc, but after a reset, every time straight back to TWRP.
Looks like I might need to flash back to stock somehow.
But I did find this, but not yet tried.
https://www.reddit.com/r/LineageOS/comments/5riech/how_fix_twrp_recovery_boot_loop_after_lineageos/
andydgg said:
Mine's exactly the same, I factory reset so I could pass the phone on; and now it will not install custom roms, I've tried about 7 or 8, and it will only boot into twrp 3.0.2-5. Soft brick, but I'm unable to find any solution.
Here's hoping someone will come and help.
I think I'll have to reinstall twrp by connecting the phone to the computer, but I've no idea how to do this.
Click to expand...
Click to collapse
Well i have took the ultimate solution. Back to stock firmware fix everything. Well, i guess not much to mention on stock firmware=)
I think you should do the same thing too. Good luck.
slifer225 said:
Well i have took the ultimate solution. Back to stock firmware fix everything. Well, i guess not much to mention on stock firmware=)
I think you should do the same thing too. Good luck.
Click to expand...
Click to collapse
That is good to know, I shall attempt to do the same, did you later install a custom rom and everything was fine afterwards?
Yes, i flashed custom recovery and ROM afterward. Even several attempt on wipe and flash the new ROM. So i guess it should be fixed
Thank you.
andydgg said:
Mine's exactly the same, I factory reset so I could pass the phone on; and now it will not install custom roms, I've tried about 7 or 8, and it will only boot into twrp 3.0.2-5. Soft brick, but I'm unable to find any solution.
Here's hoping someone will come and help.
I think I'll have to reinstall twrp by connecting the phone to the computer, but I've no idea how to do this.
Click to expand...
Click to collapse
As slifer225 mentioned you can downgrade to stock firmware by installing the stock MM rom s433 version using spftools.
Download and Install stock MM rom using spftools.
Here is the link- https://cloud.mail.ru/public/Cco5/JYk3ytrW1
For further info follow this post- https://forum.xda-developers.com/k3-...3#post71749243
Follow this step by step guide to go back to unrooted stock rom. If you want to root after that then try installing custom recovery(twrp) again using spftools and flash supersu.zip using recovery. Do take a backup though before rooting your device.
---------- Post added at 10:11 AM ---------- Previous post was at 10:04 AM ----------
justwondering said:
That is good to know, I shall attempt to do the same, did you later install a custom rom and everything was fine afterwards?
Click to expand...
Click to collapse
Everything is working perfectly as I myself had gone through the same issue and did everything to fix the problem until I downgraded back to stock. Did root on my device again and installed lineage 7.1.1 and it works like a charm. One thing I love about this rom is the efficient ram management, lag free but battery management is not upto the mark but I guess we can work it out.
Whatever you do never forget taking a backup of functional rom.
Yes, I can confirm the solution worked for me, I left it with stock rom for my friend, I tried lineage 14.1 and did a factory reset, but ended once again with softbrick , lineage will install and work perfectly, but as soon as you do a factory reset, soft brick
Now I've hard bricked it. I loaded up a 'looprecovery' when it rebooted there's nothing, no charge light no vibrations PC doesn't see it, land fill?
Wondering...
justwondering said:
Exactly the same issue here too, installed lineage 14.1, was working great, I was selling to a friend, did a factory reset, now stuck at twrp, roms install etc, but after a reset, every time straight back to TWRP.
Looks like I might need to flash back to stock somehow.
But I did find this, but not yet tried.
https://www.reddit.com/r/LineageOS/comments/5riech/how_fix_twrp_recovery_boot_loop_after_lineageos/
Click to expand...
Click to collapse
I think that solution only works on Snapdragons. It didn't for me. Is there a solution for MTK devices?
the solution for this(FIX)
all we need to do is reinstall a stock recovery and the again reinstall the TWRP
https://forum.xda-developers.com/k3-note/general/ufficial-thread-lenovo-k3-note-t3102997
follow this link..my phone just got fixed
My phone TWRP-looped many times. The solution is actually easy.
1. Reflash using SPFlashtool ONLY the stock recovery
2. boot into stock recovery
3. choose english > press reboot phone
4. phone will reboot into rom without problemos
5. reflash TWRP
cheers
or
1. Copy stock recovery.img into sdcard
2. In twrp, select Install and navigate to where you put stock recovery.img
3. Press install image. Then, Select recovery.img. Slide to install
4. boot into stock recovery
5. choose english > press reboot phone
6. phone will reboot into rom without problemos
7. reflash TWRP
DONE
Infinity loop recovery
andydgg said:
Now I've hard bricked it. I loaded up a 'looprecovery' when it rebooted there's nothing, no charge light no vibrations PC doesn't see it, land fill?
Click to expand...
Click to collapse
hI MY FRIEND , you have been able to fix your K3 note, I have the same problem, I made twrp flash and went into infinite loop. Can you help? thank you
I smashed it and put it in the bin. I think once you can't get a charge light after tyring for a couple of week, it's dead.
Not working for Lenovo K3 Note.
My K3 note stuck in the twrp recovery after factory reset from the RR. I tried this solution but it didn't work.
Please help.