Related
i have tried to installing theme end v3 update.firstly i think, i install wrong theme(probably 2.1 theme). then i tried to install another theme,but i can't do it.
now, only led is opening my device. sometimes i can enter androini menu.
i think you are understand that i am amateur android user. can you explain me what should i do step by step??
information:
milestone xt720 2.2.1 dexter froyo. stock221v13-bugfix-3 installed.
just follow the steps to install a custom ROM like Dexter 1.3
if you have open recovery installed, just boot to it, and select the option to flash the ROM again or restore from backup
i try to boot it,but when i try system backup,backup hooked system: dumping.... step.
If you can boot into (Androidiani) Open Recovery you want to wipe the dalvik-cache & if that won't get your phone to boot you need to nadroid restore a fresh copy of Dexter's froyo & the apply the patch again. Wipe the dalvik-cache & wipe data / factory reset.
how can i do it???
should i paste my sd card dexter foroyo(where in the sd card)???
sorry for my english
can you explain me step by step???please...........
oddo1907 said:
how can i do it???
should i paste my sd card dexter foroyo(where in the sd card)???
sorry for my english
Click to expand...
Click to collapse
If you were already running Dexter's Froyo the files are already on your sdcard. Boot into Open Recovery >> nandroid >> restore >> stock221v13 >> restore all. Wipe data / factory reset.
i entered nandroid >> restore but is not stock221v13 in there
3rdstring said:
If you were already running Dexter's Froyo the files are already on your sdcard. Boot into Open Recovery >> nandroid >> restore >> stock221v13 >> restore all. Wipe data / factory reset.
Click to expand...
Click to collapse
oddo1907 said:
i entered nandroid >> restore but is not stock221v13 in there
Click to expand...
Click to collapse
Re-download that from Dexter's thread and put it in the nandroid/openrecovery directory of your sdcard.
Also, avoid leaving your phone in recovery for prolonged periods, it's known to drain battery faster than it can charge!
i opened sd card my laptop. stock221v13 in there,but device not find.
oddo1907 said:
i entered nandroid >> restore but is not stock221v13 in there
Click to expand...
Click to collapse
did you try reflash to stock 2.1 with rsd ??
oddo1907,
be patient...mediaon said is correct.....start from scratch...reflash back to eclair 2.1 with rsd...and choose your favorite froyo rom
Mioze7Ae said:
Re-download that from Dexter's thread and put it in the nandroid/openrecovery directory of your sdcard.
Also, avoid leaving your phone in recovery for prolonged periods, it's known to drain battery faster than it can charge!
Click to expand...
Click to collapse
fortunately , i try to recovery for prolonged periods.now when i trried recovery, the device power off.
oddo1907 said:
fortunately , i try to recovery for prolonged periods.now when i trried recovery, the device power off.
Click to expand...
Click to collapse
Recovery(not androidini) loaded with when device is working.now should i install androidini or beforely version of open recovery???
gera_nium said:
oddo1907,
be patient...mediaon said is correct.....start from scratch...reflash back to eclair 2.1 with rsd...and choose your favorite froyo rom
Click to expand...
Click to collapse
i dont know how to reflash??? can you explain me step by step???
oddo1907 said:
i dont know how to reflash??? can you explain me step by step???
Click to expand...
Click to collapse
Hope this helps http://forum.xda-developers.com/showthread.php?t=972709&highlight=stock & http://forum.xda-developers.com/showthread.php?t=953863
yup just download those files
boot the phone and flash it back to stock with RSD lite 4.6
AllGamer said:
yup just download those files
boot the phone and flash it back to stock with RSD lite 4.6
Click to expand...
Click to collapse
I press the Powerbutton and all that happens is that the led row lights up but the screen stays black.
what do??
how can i reflash???
oddo1907 said:
I press the Powerbutton and all that happens is that the led row lights up but the screen stays black.
what do??
how can i reflash???
Click to expand...
Click to collapse
I think your battery power is now too low. This phone really has a big problem with draining battery faster than it can charge when not completely booted into a working system. The challenge is that when charging, the phone autoboots when it hits minimal energy and if it doesn't make it all the way into Android, it quickly drains itself back to square one again.
I think the surest fire way out of this trap is to get an external battery charger (I have one ordered because I'm fed up playing this battery "game").
When this happens to me (can't boot, button leds only or if you wait long enough even worse--no leds--I've been there ) I've been able to charge for a while while watching the phone like a hawk. When your phone starts to autoboot pull out the battery and put it back in. Repeat a few times. It's a super pain in the ass.
It's not safe to RSD/SBF without a full charge.
Mioze7Ae said:
I think your battery power is now too low. This phone really has a big problem with draining battery faster than it can charge when not completely booted into a working system. The challenge is that when charging, the phone autoboots when it hits minimal energy and if it doesn't make it all the way into Android, it quickly drains itself back to square one again.
I think the surest fire way out of this trap is to get an external battery charger (I have one ordered because I'm fed up playing this battery "game").
When this happens to me (can't boot, button leds only or if you wait long enough even worse--no leds--I've been there ) I've been able to charge for a while while watching the phone like a hawk. When your phone starts to autoboot pull out the battery and put it back in. Repeat a few times. It's a super pain in the ass.
It's not safe to RSD/SBF without a full charge.
Click to expand...
Click to collapse
any alternatif solution suggestion??
because buying external charger is extremely difficult for me. i am live in turkey
A couple of weeks ago I decided to root my phone for the benefits it came with. I did so successfully and had no problems until I decided I'd let my curiosity get the better of me and try flashing CM7 onto my phone. I did so, and everything seemed successful, but I got stuck in a boot loop when I turned on the phone.
I know there are solutions to this, but they all involve either CWM or ADB. Just two problems: I can't use ADB because I forgot to leave USB Debugging on, and I can't seem to get CWM to do anything (it's just a black screen).
There are solutions to all of these problems individually, I know, but each solution relies on at least one of the others to be working. I've been surfing this forum and others like it hoping that someone else would have this problem and would have a solution for me, but I've come up dry.
I used attn1's Ace Hack to root my phone, and then I used Rom Manager to install CM7. Then I hit the loop. Also, my CWM was working prior to CM7.
Does anyone know what I should do?
Thank you in advance,
JW
Inspire 4g
P.S. - I'm new to this forum and don't really know the rules perfectly, so if I did something wrong, then please just let me know what I did and what I should've done. Thank you.
But you can still get in hboot right?
It sounds like you did not choose to wipe data and cache. You always need to do this when changing roms. Best way is to enter cwm yourself and select wipe data/factory reset and wipe dalvik then flash Rom.
Pull you battery for a little bit then try and get into recovery again. If you still can't get in then you will have to reflash your recovery through bootloader.
If all else fails you can use the tool in this link to return to stock. Then re root you phone. genes tool
You can jump into the IRC channel and get some real-time help too:
http://webchat.freenode.net/?channels=#liberatedAria
Gizmoe said:
It sounds like you did not choose to wipe data and cache. You always need to do this when changing roms. Best way is to enter cwm yourself and select wipe data/factory reset and wipe dalvik then flash Rom.
Click to expand...
Click to collapse
No, I didn't think to. To be honest, I saw Rom Manager and thought I would just be able to click on what I wanted and have it ready to play with in a few minutes. I never read what to do before the installation, which was my huge mistake.
Anyhow, I don't think I can get into HBoot. When I turn the phone on with power button and volume button, it vibrates three times, but then it goes to a black screen. I read about this problem with CWM, but the only solutions I saw involved getting into your phone - which I can't do.
So I'm wondering if CWM still works but that it just doesn't show what it's doing. If that's the case, then maybe I could still manage to fix my phone with CWM. Does anyone know if such is the case?
Thank you!
Gizmoe said:
If all else fails you can use the tool in this link to return to stock. Then re root you phone. genes tool
Click to expand...
Click to collapse
Gene Poole said:
You can jump into the IRC channel and get some real-time help too:
http://webchat.freenode.net/?channels=#liberatedAria
Click to expand...
Click to collapse
Thank you both so much for your help! I'm sorry I'm such an ignoramus. Thank you guys!!
JesseWright said:
No, I didn't think to. To be honest, I saw Rom Manager and thought I would just be able to click on what I wanted and have it ready to play with in a few minutes. I never read what to do before the installation, which was my huge mistake.
Anyhow, I don't think I can get into HBoot. When I turn the phone on with power button and volume button, it vibrates three times, but then it goes to a black screen. I read about this problem with CWM, but the only solutions I saw involved getting into your phone - which I can't do.
So I'm wondering if CWM still works but that it just doesn't show what it's doing. If that's the case, then maybe I could still manage to fix my phone with CWM. Does anyone know if such is the case?
Click to expand...
Click to collapse
Sounds like you're holding the vol+ button. You need to be holding vol- when you press power to get to HBOOT. From there you can get into Recovery.
sharksfan7 said:
Sounds like you're holding the vol+ button. You need to be holding vol- when you press power to get to HBOOT. From there you can get into Recovery.
Click to expand...
Click to collapse
this is correct, but you may want to pull out your sd card first. if it still has the pd98img on there,,, its just gonna loop ya. so pull it out before trying, you can always stick it back in once you get to recovery, then select mount> sd card
GOOD LUCK!!
Hi there. I had a stock S4g, had froyo 2.2.1. I Rooted the phone. That went fine. I went to install a new kernel (baliSGS4G) The instal got interrupted, second reboot had the android logo flashing while the normal galaxy s logo was on, so I knew from there it was screwed up...
It booted up fine actually, and i was able to operate around in on the phone, altho the home button didnt work... I went ahead and tried a restart to see what it would do and it would stick at the galaxy s boot screen and the voice would say "restore operation" and just reboot and be stuck on a boot loop...
I CANNOT get into recovery mode UNLESS I remove my sdcard... if I do I CAN... BUT it seems as tho the cwm recover is somewhat useless to me now that the sdcard isnt in.... If I boot into recovery and THEN put the card in, it saws E: Can't mount /sdcard..
Ive tried wipe cache partition, wipe data/factory reset... nothing..
Any suggestions? THankyou!
use any one of the "one clicks".
p.s. gb is a better os
Sent from my Nexus 4 using xda premium
sorry, i've very novice, what do you mean by the one clicks? Like a one click flash program or something?
And yeah, I actually have a galaxy SIII.....the reason i grabbed this one out is i have a little go pro style project im going to do with it and dont want to risk breaking my new phone.
I will try the newer os If i can get this fixed.. Hopefully!
Superbeeblaze said:
sorry, i've very novice, what do you mean by the one clicks? Like a one click flash program or something?
And yeah, I actually have a galaxy SIII.....the reason i grabbed this one out is i have a little go pro style project im going to do with it and dont want to risk breaking my new phone.
I will try the newer os If i can get this fixed.. Hopefully!
Click to expand...
Click to collapse
Second link in signature will help.
Ok Lumin, I did what you said and I am getting to the command promt and it is not seeing my phone, It still shows the phone is disconnected... I have CWM recovery, is that an issue?? That opens when i hold the up,down,up button combo, not the stock download mode screen.
Very well written tutorial btw.
[/COLOR]
Superbeeblaze said:
Hi there. I had a stock S4g, had froyo 2.2.1. I Rooted the phone. That went fine. I went to install a new kernel (baliSGS4G) The instal got interrupted, second reboot had the android logo flashing while the normal galaxy s logo was on, so I knew from there it was screwed up...
It booted up fine actually, and i was able to operate around in on the phone, altho the home button didnt work... I went ahead and tried a restart to see what it would do and it would stick at the galaxy s boot screen and the voice would say "restore operation" and just reboot and be stuck on a boot loop...
I CANNOT get into recovery mode UNLESS I remove my sdcard... if I do I CAN... BUT it seems as tho the cwm recover is somewhat useless to me now that the sdcard isnt in.... If I boot into recovery and THEN put the card in, it saws E: Can't mount /sdcard..
Ive tried wipe cache partition, wipe data/factory reset... nothing..
Any suggestions? THankyou!
Click to expand...
Click to collapse
Try One-Click Gremlin Remover to flash and fix. Found this to be easier than Heimdall for the uninitiated: http://forum.xda-developers.com/showthread.php?t=1500427
1 Open Gremlin remover on PC
2. Remove battery from phone
3. Hold down both the Up and Down on the Volume Rocker
4. Plug Phone into USB (without battery)
5. Insert battery into phone and replace cover
The phone should automatically boot into Download mode, and Gremlin Remover should recognize the phone. This should wipe it back to stock but leave it rooted. Then you can start again. I recommend the SGS Kernel Flasher App to flash new kernels in the future. Much less prone to error.
OK its late, i wasnt reading close enough, I was holding the power button too like an idiot... Got it to work, now my phone boots up like new.
Thanks for the help guys.
I can sleep well tonight. :laugh::good:
ariesgodofwar said:
[/COLOR]Try One-Click Gremlin Remover to flash and fix. Found this to be easier than Heimdall for the uninitiated: http://forum.xda-developers.com/showthread.php?t=1500427
1 Open Gremlin remover on PC
2. Remove battery from phone
3. Hold down both the Up and Down on the Volume Rocker
4. Plug Phone into USB (without battery)
5. Insert battery into phone and replace cover
The phone should automatically boot into Download mode, and Gremlin Remover should recognize the phone. This should wipe it back to stock but leave it rooted. Then you can start again. I recommend the SGS Kernel Flasher App to flash new kernels in the future. Much less prone to error.
Click to expand...
Click to collapse
You might refrain from recommending a different flashing utility (ODIN) when somebody has already started using Heimdall and is just asking for help to finish the process. All you are doing is inviting more problems with driver and USB port issues by doing so. You gave him a simple set of instructions that mentioned nothing about drivers.
And SGS Kernel Flasher is great but it only works properly on our GB ROMs.
lumin30 said:
You might refrain from recommending a different flashing utility (ODIN) when somebody has already started using Heimdall and is just asking for help to finish the process. All you are doing is inviting more problems with driver and USB port issues by doing so. You gave him a simple set of instructions that mentioned nothing about drivers.
And SGS Kernel Flasher is great but it only works properly on our GB ROMs.
Click to expand...
Click to collapse
Oops! Wasn't me.
Sent from my SGH-T959V using xda premium
Hi, last night my wifi seemed to cut off while using my tablet. I tried to cut it back on and it got stuck in the "trying to connect to wifi" stage. I cant press the button and it wont turn back on. I was running Chromi X 4.6.6 at the time. Today, I flashed 4.6.8, hoping it would reset and fix the problem, but the problem still is there. I am really nervous I broke my wifi chip or something. Here is a screenshot of what is happening. I hope someone can help me.
Thank you.
wl123 said:
Hi, last night my wifi seemed to cut off while using my tablet. I tried to cut it back on and it got stuck in the "trying to connect to wifi" stage. I cant press the button and it wont turn back on. I was running Chromi X 4.6.6 at the time. Today, I flashed 4.6.8, hoping it would reset and fix the problem, but the problem still is there. I am really nervous I broke my wifi chip or something. Here is a screenshot of what is happening. I hope someone can help me.
Thank you.
Click to expand...
Click to collapse
Is the WiFi icon greyed out in the bottom right? If so try removing your Google account from settings and the readd it. I think Google have been having some DNS issues recently.
sbdags said:
Is the WiFi icon greyed out in the bottom right? If so try removing your Google account from settings and the readd it. I think Google have been having some DNS issues recently.
Click to expand...
Click to collapse
I removed my Google account and tried to re add it. I get to the part where I need to be connected to wifi and I get this. Something seems to be horribly wrong.
wl123 said:
I removed my Google account and tried to re add it. I get to the part where I need to be connected to wifi and I get this. Something seems to be horribly wrong.
Click to expand...
Click to collapse
Do you have a back up nandroid to go back to? Try a clean wipe as well to eliminate software issues.
sbdags said:
Do you have a back up nandroid to go back to? Try a clean wipe as well to eliminate software issues.
Click to expand...
Click to collapse
Yes I have a backup from like chromi 4.5. I am trying to restore right now. If I clean wipe it, wont it delete the nandroid backups?
wl123 said:
Yes I have a backup from like chromi 4.5. I am trying to restore right now. If I clean wipe it, wont it delete the nandroid backups?
Click to expand...
Click to collapse
Just do a factory wipe. As long as you don't do a full data wipe you will keep your nandroids if they are on internal.
This :http://www.transformerforums.com/fo...h-will-not-turn-asus-say-start-over-help.html
is exactly the same problem I am having.
sbdags said:
Just do a factory wipe. As long as you don't do a full data wipe you will keep your nandroids if they are on internal.
Click to expand...
Click to collapse
How long does it usually take to Restore Data when restoring a nandroid backup? It seems to be taking a long time
wl123 said:
How long does it usually take to Restore Data when restoring a nandroid backup? It seems to be taking a long time
Click to expand...
Click to collapse
15 mins... ish
BTW you don't need to wipe when restoring as it does that for you automatically.
sbdags said:
15 mins... ish
BTW you don't need to wipe when restoring as it does that for you automatically.
Click to expand...
Click to collapse
**** me. Restored back to 4.6.4. Wifi is still broken. Gets to the the "Turning Wi-Fi- on..." screen and never turns on. I am freaking out.
Do you think doing this will work? And if so, how do I start a terminal session?
I've had the Bluetooth not turning on issue four times on my TF101 - the first two times a hard reset (no data loss) fixed it - have you tried this, as opposed to a restart? - and the next two times I just waited and eventually BT turned on. I've never encountered this with WiFI (yet).
In case anyone else encounters this, on a rooted tablet the following might also help:
Open a terminal session and -
su - <enter>
cd /system/bin <enter>
stop bluetoothd <enter>
start bluetoothd -n <enter>
This will force stop and then restart the Bluetooth daemon. I haven't yet worked out (mainly because I haven't need to) what the equivlent process is for WiFi.
wl123 said:
**** me. Restored back to 4.6.4. Wifi is still broken. Gets to the the "Turning Wi-Fi- on..." screen and never turns on. I am freaking out.
Do you think doing this will work? And if so, how do I start a terminal session?
I've had the Bluetooth not turning on issue four times on my TF101 - the first two times a hard reset (no data loss) fixed it - have you tried this, as opposed to a restart? - and the next two times I just waited and eventually BT turned on. I've never encountered this with WiFI (yet).
In case anyone else encounters this, on a rooted tablet the following might also help:
Open a terminal session and -
su - <enter>
cd /system/bin <enter>
stop bluetoothd <enter>
start bluetoothd -n <enter>
This will force stop and then restart the Bluetooth daemon. I haven't yet worked out (mainly because I haven't need to) what the equivlent process is for WiFi.
Click to expand...
Click to collapse
I got that problem before. I believed that this was what I did if you want to try it out:
1. Wipe both Caches and data
2. Restart your system
3. Shut it off again
4. Go to recovery and select the Android for a cold boot
5. Restart it again and it work for me
I don't know why I had to go through that sequences but I seem to work for me, good luck.
LetMeKnow said:
I got that problem before. I believed that this was what I did if you want to try it out:
1. Wipe both Caches and data
2. Restart your system
3. Shut it off again
4. Go to recovery and select the Android for a cold boot
5. Restart it again and it work for me
I don't know why I had to go through that sequences but I seem to work for me, good luck.
Click to expand...
Click to collapse
Thanks im about to try.
Q1: How do you wipe cache and data without reset?
So, Wipe, Restart, Turn back off. Restart into recovery and select android for a cold boot? What do you mean by that?
wl123 said:
Thanks im about to try.
Q1: How do you wipe cache and data without reset?
So, Wipe, Restart, Turn back off. Restart into recovery and select android for a cold boot? What do you mean by that?
Click to expand...
Click to collapse
1. Restart into your recovery, assuming TWRP, and select Wipe option in your recovery
2. When you boot into recovery, there are 3 icons, the middle icon is the android that I am talking about
Hope that helps
LetMeKnow said:
1. Restart into your recovery, assuming TWRP, and select Wipe option in your recovery
2. When you boot into recovery, there are 3 icons, the middle icon is the android that I am talking about
Hope that helps
Click to expand...
Click to collapse
Everytime I restart to recovery, it loads TWRP. I see a little android icon as it is booting, but its not like I can click on him. When I wiped using TWRP, it did a factory reset. I restarted to system, but the damn wifi is still not working. I am so frustrated.
Thank you for your help. I am going to eat and drink a beer and try again later.
wl123 said:
Everytime I restart to recovery, it loads TWRP. I see a little android icon as it is booting, but its not like I can click on him. When I wiped using TWRP, it did a factory reset. I restarted to system, but the damn wifi is still not working. I am so frustrated.
Thank you for your help. I am going to eat and drink a beer and try again later.
Click to expand...
Click to collapse
Hehe, I have been there so many times before. You can use the volume up to select and volume down to confirm. Any way, did you tweak your device before the problem? Did you use D2SD? Maybe you explain a little more details what you did so that people have better understanding of your problem. The worse case is you have to flash the rom again .
LetMeKnow said:
Hehe, I have been there so many times before. You can use the volume up to select and volume down to confirm. Any way, did you tweak your device before the problem? Did you use D2SD? Maybe you explain a little more details what you did so that people have better understanding of your problem. The worse case is you have to flash the rom again .
Click to expand...
Click to collapse
I was not running Data2SD (at least I dont think). I just figured out how to cold boot android. Do you think this could be a hardware issue with my wireless card? It seems to me like it has to be some sort of software bug
wl123 said:
I was not running Data2SD (at least I dont think). I just figured out how to cold boot android. Do you think this could be a hardware issue with my wireless card? It seems to me like it has to be some sort of software bug
Click to expand...
Click to collapse
I had that problem before. Therefore, I am very sure that it is a program bug. Do you use Micro SD in your tablet? When I tweak my tablet, there are all kinds of problems that I have encountered. If you give me some more details, I might be able to help you out.
LetMeKnow said:
I had that problem before. Therefore, I am very sure that it is a program bug. Do you use Micro SD in your tablet? When I tweak my tablet, there are all kinds of problems that I have encountered. If you give me some more details, I might be able to help you out.
Click to expand...
Click to collapse
OK. I was running Chromi-X 4.6.6 ODEX at the time it happened. I used to use a micro sd card but it was acting weird and I took it out. I have been using only the internal SD for the last ~3 months. I use _that/ stock modded kernel variant based from ASUS Stock that comes with the ChromiX mod. I run Apex launcher. Android version 4.2.1.
Using TWRP 2.5 on 10.6.1.14.4 via goomanager.
So far I have tried:
- Flashing ChromiX 4.6.8
- Recovering an old nandroid backup (4.6.4)
- Clearing cache and data via TWRP and restarting with cold boot
wl123 said:
OK. I was running Chromi-X 4.6.6 ODEX at the time it happened. I used to use a micro sd card but it was acting weird and I took it out. I have been using only the internal SD for the last ~3 months. I use _that/ stock modded kernel variant based from ASUS Stock that comes with the ChromiX mod. I run Apex launcher. Android version 4.2.1.
Using TWRP 2.5 on 10.6.1.14.4 via goomanager.
So far I have tried:
- Flashing ChromiX 4.6.8
- Recovering an old nandroid backup (4.6.4)
- Clearing cache and data via TWRP and restarting with cold boot
Click to expand...
Click to collapse
If you don't mind, you can try a clean install.
1. Boot back into twrp and select wipe, use format option instead of wipe
2. Install cromi x, prefer 3.6.5
3. After the installation is completed, restart your tablet and leave it there for a few minutes
4. Make sure that you must SHUT IT OFF COMPLETELY for a few seconds and turn it back on
Hope it will solve your problem, good luck.
LetMeKnow said:
If you don't mind, you can try a clean install.
1. Boot back into twrp and select wipe, use format option instead of wipe
2. Install cromi x, prefer 3.6.5
3. After the installation is completed, restart your tablet and leave it there for a few minutes
4. Make sure that you must SHUT IT OFF COMPLETELY for a few seconds and turn it back on
Hope it will solve your problem, good luck.
Click to expand...
Click to collapse
Regarding #2. Where would I find a download of chromix 3.6.5?
Holy ****.
I just rebooted into TWRP before formating, and then rebooting back to system to save my pictures, and all of a sudden the WiFi is working again. Going to flash the latest Chromi X and see what happens
I was on Cromi-x 4.7 and everything was smooth.i decided to move on and test the new beta 5.
when i flashed everything was normal and i was on haunds kernel 3.2
it suddenly restartet and got stuck on the asus logo.
i tried everything!changing kernel.changed the rom and even went back to the stock rom and none of them worked for me
and now its stuck on asus logo and its in a restart loop....
i'm really disappointed:/
is it a hardbrick or what??
what should i do???
p.s:i have access to my twrp 2.5 recovery..
Can you hold down power and volume down and get to the bootlloader menu? The one with the RCK menu?
sbdags said:
Can you hold down power and volume down and get to the bootlloader menu? The one with the RCK menu?
Click to expand...
Click to collapse
yes
i have access to bootloader and recovery
original1371 said:
yes
i have access to bootloader and recovery
Click to expand...
Click to collapse
Then you are not hard bricked
Which recovery are you using?
Easiest method is probably go into wipes and do a factory wipe, then reinstall the rom but choose that's or my stock kernel and see if that boots first.
sbdags said:
Then you are not hard bricked
Which recovery are you using?
Easiest method is probably go into wipes and do a factory wipe, then reinstall the rom but choose that's or my stock kernel and see if that boots first.
Click to expand...
Click to collapse
thanks for fast reply!
TWRP 2.5
i did that.wiped everything and reinstalled the rom once with That then with stock and last haunds and none of them worked for me!it just freezes on asus logo and restrat and restarts and restarts.:/ any idea?:s
original1371 said:
thanks for fast reply!
TWRP 2.5
i did that.wiped everything and reinstalled the rom once with That then with stock and last haunds and none of them worked for me!it just freezes on asus logo and restrat and restarts and restarts.:/ any idea?:s
Click to expand...
Click to collapse
Try this:
1. Reboot to recovery
2. Select Mount and uncheck System, Cache and Data
3. Go to Advanced, then Terminal Command, then hit Select Folder to start Terminal
4. type "e2fsck -fvyD /dev/block/mmcblk0p8" and press return. Wait for the process to finish (this is for Data)
5. type "e2fsck -fvyD /dev/block/mmcblk0p2" and press return. Wait for the process to finish (this is for Cache)
6. type "e2fsck -fvyD /dev/block/mmcblk0p1" and press return. Wait for the process to finish (this is for System)
Click to expand...
Click to collapse
Then try wiping and reflashing a ROM.
well i am doing what you said
it is in data part for a long time and i am still waiting
hope it works!:-s
original1371 said:
well i am doing what you said
it is in data part for a long time and i am still waiting
hope it works!:-s
Click to expand...
Click to collapse
If you have a corrupted data partition it may take a long time.
sbdags said:
If you have a corrupted data partition it may take a long time.
Click to expand...
Click to collapse
well...that doesnt work:| still freezes on logo and restarts on and on
does formating internal memory help?
any other idea??
original1371 said:
well...that doesnt work:| still freezes on logo and restarts on and on
does formating internal memory help?
any other idea??
Click to expand...
Click to collapse
If you format your internal SD, it will solve a lot of unknown problems that I don't know how to fix or a root cause of it.. However, you will loose all your personal data and files. By any chance do you use 64G external SD?
LetMeKnow said:
If you format your internal SD, it will solve a lot of unknown problems that I don't know how to fix or a root cause of it.. However, you will loose all your personal data and files. By any chance do you use 64G external SD?
Click to expand...
Click to collapse
well.formating will be my last straw i think
no i dont use sd card at all
original1371 said:
well.formating will be my last straw i think
no i dont use sd card at all
Click to expand...
Click to collapse
Can you check this out for me? Boot back into the TWRP and look under Mount to see if any check boxes are unchecked, especially the System.
LetMeKnow said:
Can you check this out for me? Boot back into the TWRP and look under Mount to see if any check boxes are unchecked, especially the System.
Click to expand...
Click to collapse
now i booted back into the twrp and system was unchecked
data and cache were checked
original1371 said:
now i booted back into the twrp and system was unchecked
data and cache were checked
Click to expand...
Click to collapse
It is why that you can not boot into your system because your system was not mounted.. You can try wipe both caches and power off your device completely for about 15 second. You can power it back on with your power button to see if it works..
sbdags said:
If you have a corrupted data partition it may take a long time.
Click to expand...
Click to collapse
If you have lots of files on the data partition, it may take a long time, even if everything is fine.
original1371 said:
well.formating will be my last straw i think
no i dont use sd card at all
Click to expand...
Click to collapse
*sigh*
Everybody should read this: http://forum.xda-developers.com/showpost.php?p=39476212&postcount=4104
LetMeKnow said:
It is why that you can not boot into your system because your system was not mounted..
Click to expand...
Click to collapse
No. The recovery is independent from Android, and Android mounts the system partition itself.
LetMeKnow said:
You can try wipe both caches and power off your device completely for about 15 second. You can power it back on with your power button to see if it works..
Click to expand...
Click to collapse
*sigh*
http://forum.xda-developers.com/showpost.php?p=39473157&postcount=4099
_that said:
If you have lots of files on the data partition, it may take a long time, even if everything is fine.
*sigh*
Everybody should read this: http://forum.xda-developers.com/showpost.php?p=39476212&postcount=4104
No. The recovery is independent from Android, and Android mounts the system partition itself.
*sigh*
http://forum.xda-developers.com/showpost.php?p=39473157&postcount=4099
Click to expand...
Click to collapse
Thanks again _that. I always learn from your post. However, this is not a Development forum and sometime if you are too technical, it is more confused than helping someone else.. It is my two cents.. :fingers-crossed:
LetMeKnow said:
It is why that you can not boot into your system because your system was not mounted.. You can try wipe both caches and power off your device completely for about 15 second. You can power it back on with your power button to see if it works..
Click to expand...
Click to collapse
no,it didnt help!
_that said:
Everybody should read this: http://forum.xda-developers.com/showpost.php?p=39476212&postcount=4104
Click to expand...
Click to collapse
thank for your help.
well,according to your post, my problem is |boot loop| cause its rebooting and never goes further than the asus logo!
so what should i do now? where should i write |adb shell cat /proc/last_kmsg > last_kmsg.txt|?? in fastmode?? where is adb that you are talkin about?
sorry if i sound noob here,i dont have enough info about this
LetMeKnow said:
However, this is not a Development forum and sometime if you are too technical, it is more confused than helping someone else..
Click to expand...
Click to collapse
This is XDA Developers. "XDA Developers was founded by developers, for developers."
I don't expect everyone to be a developer, but I expect people here to have some knowledge about using computers that exceeds clicking icons in Windows and being able to open a browser.
As super mod zelendel wrote, "XDA is a place to come to learn and share your knowledge. If you are not here for those reasons then you are here for the wrong ones.". I know you are here for the right reasons.
If something in my postings is too technical, just ask - I am happy to explain anything.
original1371 said:
no,it didnt help!
thank for your help.
well,according to your post, my problem is |boot loop| cause its rebooting and never goes further than the asus logo!
so what should i do now? where should i write |adb shell cat /proc/last_kmsg > last_kmsg.txt|?? in fastmode?? where is adb that you are talkin about?
sorry if i sound noob here,i dont have enough info about this
Click to expand...
Click to collapse
Time to take a breather anyway, I think. Take this opportunity to learn the basics about adb. You can start here:
http://forum.xda-developers.com/showthread.php?t=2303834
If you get stuck, just ask.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Usually a data format and reflash of system will fix this type of bootloop. You didn't by any chance flash a new bootloader did you when you were trying to fix it? Have you tried restoring a nandroid at all?
I'm all out of ideas. I've fixed many bootloops now so we should be able to get you up and running but something doesn't quite compute.....