[Q] I bricked my tablet now it freezes at bootloader screen - Acer Iconia A500

So Today i just installed v8 ics bootloader on my acer a500 and i was very happy because after one month of trying auto way and failing i tried manual way and it worked :laugh:
so i installed cwm then i wanted to install a rom
at the wipes i choose
Dalvik Cache
then i asked it to backup my first rom
so it went into the bootloader mode and after like 20 mins said that backup failed because of a reason i can't remember .
then it restarted and it just freezes at the bootloader screen .
and whenever i restart or anything just freezes at bootloader screen. :crying:
is there anything i could do to fix it ? even if it includes wiping all of my data?
I am new to android I know I probably just did something very stupid but we all do mistake and learn.

I suggest installing whatever rom you were planing on installing after your backup, that might fix your boot problem. I also suggest flashing and using TWRP recovery, Cwm would never backup my flexrom partition but TWRP always backs it up and i never have issues making a backup or restoring from a backup since using twrp. Use TWRP 1.7.- as some problems arise when using the 2.2- versions..
I used the afterota to install twrp over the cwm recovery but you might not need to.
Good luck and if i can help you i will if issues arise.

Please I am a noob can u tell me how to do that in very boring details ?

now after a little button pressing thanks to ur idea it gpt fixed.
thanks alot

sasori962008 said:
now after a little button pressing thanks to ur idea it gpt fixed.
thanks alot
Click to expand...
Click to collapse
Happy that it worked for you.

Related

stuck in recovery

i flashed the CWM update zip, booted into CWM, wiped, and now im trying to install the EOS rom
it goes smoothly and i get no errors, but it boots into CWM every single boot now.,,
Pushed the older 6006 cwm and flashed, no errors, still boots into 6010.. ?
http://forum.xda-developers.com/showthread.php?p=22897771
Found this thread. For transformer Prime but hopefully it fixes my issue. If this is a bad idea lmk.
If not, Will try around midnight when I get back home
Woops,
Found this too
http://forum.xda-developers.com/showthread.php?t=1781250
Did you flash the CWM.zip in TWRP? I ask because there was a known issue when flashing CWM from TWRP you would get stuck in a recovery loop. I had the same issue and had to flash the stock .img to get out of it. Good luck.
i flashed the CWM zip that was posted in the CWM thread, bout to try and get myself free..
::success.
booted into bootloader
flashed bootloader, restarted, booted into my rom...
rebooted back into bootloader
flashed recovery
wipe/flash normally
I'm in the same exact situation, Could you share with me how you got it to boot into bootloader? I've been trying for awhile now. As I'm stuck in CWM I'm thus far unable to use adb. I'm a total adb noob so there is probably something quite simple I'm missing. Thanks in advance for any help.
Vektor67 said:
I'm in the same exact situation, Could you share with me how you got it to boot into bootloader? I've been trying for awhile now. As I'm stuck in CWM I'm thus far unable to use adb. I'm a total adb noob so there is probably something quite simple I'm missing. Thanks in advance for any help.
Click to expand...
Click to collapse
Press volume down when it boots (right before and while the Google logo shows up)
jamesst20 said:
Press volume down when it boots (right before and while the Google logo shows up)
Click to expand...
Click to collapse
Thanks for the reply, I've tried that many times. It's not working. I wish I had read this thread carefully and learned that it might be dangerous to flash cwm zip from TWRP, I had no idea.
The thing is is that it never really shuts down properly(thought I remembered a power off option on one of my epic 4g cwm) So when I press the power button while on the reboot system now option, that is what it does but back to recovery. I tried the volume button as you suggested as well as every other combination I could think of. :~(
Well in messing with drivers(uninstalling old drivers/devices installing universal naked driver) I had the nexus 7 q3 tool waiting for adb to enter fastboot and reflash TWRP so I could restore) and the tool suceeded in kicking me into fastboot(with an error in the toolkit) The toolkit stopped communicating though. I want to use the toolkit to reflash back to stock now that I'm in the bootloader screen.
I'm a bit nervous though, some warning about flashing asus stock blobs being a sure way to HardBrick. I think I'll wait until I get better information. I am on the bootloader screen, but I'm certain my bootloader as it sits is messed up from flashing CWM.
*Edit* Success!! I used this ; "[Guide] Returning to Stock and/or Unbricking your device"located here, http://forum.xda-developers.com/showthread.php?t=1781250 (not sure how to go about inserting a descriptive link sry :~( I'm now back to stock and ready to brick it again...umm, I mean, root and flash like there's no tomorrow. hehe Thanks for the input.:good::good:

Help! CWM not installed properly?! Bricked devices?

Hi folks,
5 day ago i rootet my tablet 16GB WE and installed Koshu`s CWM step by step like discribed in his threat [http://forum.xda-developers.com/showthread.php?t=1831161]. At the end there was an error message..., i was too quick and made an reboot bevor i could read it.
But i tested if i rooted the tablet succesfully and the superuser-app said that i am root now....
Then i installed the v.0.8.1 Version and everything was fine!
a few days later i got reboots during normal use.
Now i cant boot in the OS, there are bootloops the hole time.
I think that i have not installed the CWM correct...
Any ways to check this with adb commands or something else?
It would be great if someone could help me....
Sorry for my bad english!
Thomas
tpauli said:
Hi folks,
5 day ago i rootet my tablet 16GB WE and installed Koshu`s CWM step by step like discribed in his threat [http://forum.xda-developers.com/showthread.php?t=1831161]. At the end there was an error message..., i was too quick and made an reboot bevor i could read it.
But i tested if i rooted the tablet succesfully and the superuser-app said that i am root now....
Then i installed the v.0.8.1 Version and everything was fine!
a few days later i got reboots during normal use.
Now i cant boot in the OS, there are bootloops the hole time.
I think that i have not installed the CWM correct...
Any ways to check this with adb commands or something else?
It would be great if someone could help me....
Sorry for my bad english!
Thomas
Click to expand...
Click to collapse
You can still boot into CWM? Well you could make a backup of the installed recovery (like shown in the CWM thread) and check if the md5sums are equal to the downloaded image. Btw. linebreaks in the logcat would really help reading it
Koshu said:
You can still boot into CWM? Well you could make a backup of the installed recovery (like shown in the CWM thread) and check if the md5sums are equal to the downloaded image. Btw. linebreaks in the logcat would really help reading it
Click to expand...
Click to collapse
yes i can Boot into CWM, but i cant restore my backup. I tried to install cm10 clean again but after rebooting CWM and booting the OS Android is updating the apps. But i did a full wipe bevor.Thats why i think that the CWM is not in an good state.
i am in the road and maybe i can later check the md5sum.
I can attach an picture from the CWM during trying formating and fixing permissions.
thank you!
Problem solved
tpauli said:
yes i can Boot into CWM, but i cant restore my backup. I tried to install cm10 clean again but after rebooting CWM and booting the OS Android is updating the apps. But i did a full wipe bevor.Thats why i think that the CWM is not in an good state.
i am in the road and maybe i can later check the md5sum.
I can attach an picture from the CWM during trying formating and fixing permissions.
thank you!
Click to expand...
Click to collapse
Koshu helped me! The problem was, that my data partion was read only and my wipes befor and installs was more or less unusefull!
Big thanks to koshu!!!!!
tpauli said:
Koshu helped me! The problem was, that my data partion was read only and my wipes befor and installs was more or less unusefull!
Big thanks to koshu!!!!!
Click to expand...
Click to collapse
Hi. I have the same Problem. Can you tell me how Koshu helped to fix the problem.
the checksum and stuff. thx
florian1985 said:
Hi. I have the same Problem. Can you tell me how Koshu helped to fix the problem.
the checksum and stuff. thx
Click to expand...
Click to collapse
I linked a zip file in the CM10 Thread that formats the data partition: http://forum.xda-developers.com/showthread.php?t=1846044
You can find it in the "addition steps" section. Beware that it will delete all your personal data including the internal sd-card (also nandroid backups if you have stored them on the internal sdcard). So make sure you have EXTERNAL backups if you want to keep some of the data.
I have same problem
After install CM10 ,my TPT cant boot
I turn on My tablet and see loop forever logo : Lenovo ==> CyanogenMod....
Please help me, how to fix it ????
cachlanhuong said:
I have same problem
After install CM10 ,my TPT cant boot
I turn on My tablet and see loop forever logo : Lenovo ==> CyanogenMod....
Please help me, how to fix it ????
Click to expand...
Click to collapse
I have nearly the same problem.
I rooted my TPT a few weeks ago, today I was reading about Cyanogen and decided to install CWM. After some issues with the adb drivers, I managed to install the clockwork recovery.
Now I followed the steps from the cm-thread. I did a nandroid backup and wiped my tablet. After that, I flashed CM10. But all I get is the CyanogenMod logo spinning around.
I tried to go back to my nandroid backup, but it seems broken somehow.
I also tried several several CM-versions and downloaded them several times, without success. But I realised, that the installation procedure of CM was very quick, too quick maybe? Could it be that my clockworkmod isn't installed correctly, because the installation of CM and the nandroid backup won't work.
I hope you guys can help me out. Because I only could find nandroid backups for ROW and US version. I also don´t have adb access anymore.
TPT 16GB 3G WE
Ottilooping said:
I have nearly the same problem.
I rooted my TPT a few weeks ago, today I was reading about Cyanogen and decided to install CWM. After some issues with the adb drivers, I managed to install the clockwork recovery.
Now I followed the steps from the cm-thread. I did a nandroid backup and wiped my tablet. After that, I flashed CM10. But all I get is the CyanogenMod logo spinning around.
I tried to go back to my nandroid backup, but it seems broken somehow.
I also tried several several CM-versions and downloaded them several times, without success. But I realised, that the installation procedure of CM was very quick, too quick maybe? Could it be that my clockworkmod isn't installed correctly, because the installation of CM and the nandroid backup won't work.
I hope you guys can help me out. Because I only could find nandroid backups for ROW and US version. I also don´t have adb access anymore.
TPT 16GB 3G WE
Click to expand...
Click to collapse
Koshu helped me!
I linked a zip file in the CM10 Thread that formats the data partition: http://forum.xda-developers.com/showthread.php?t=1846044
You can find it in the "addition steps" section. Beware that it will delete all your personal data including the internal sd-card (also nandroid backups if you have stored them on the internal sdcard). So make sure you have EXTERNAL backups if you want to keep some of the data.
tpauli said:
Koshu helped me!
I linked a zip file in the CM10 Thread that formats the data partition: http://forum.xda-developers.com/showthread.php?t=1846044
You can find it in the "addition steps" section. Beware that it will delete all your personal data including the internal sd-card (also nandroid backups if you have stored them on the internal sdcard). So make sure you have EXTERNAL backups if you want to keep some of the data.
Click to expand...
Click to collapse
But how can formatting my data partition help? You mean after a format, the installation of cm would work?
And how do I use the .zip, just flashing with cwm?
Ottilooping said:
But how can formatting my data partition help? You mean after a format, the installation of cm would work?
And how do I use the .zip, just flashing with cwm?
Click to expand...
Click to collapse
You have to download the formatdata.zip on your external sd-card.
After that you can boot in the recovery and flash this .please dont juse the cwm! Do you know how to boot into the recovery?
Power on and during that you should drop-down the volume + key a few seconds.
This helped me and others.
Please read in this threat: http://forum.xda-developers.com/showthread.php?t=1831161
tpauli said:
You have to download the formatdata.zip on your external sd-card.
After that you can boot in the recovery and flash this .please dont juse the cwm! Do you know how to boot into the recovery?
Power on and during that you should drop-down the volume + key a few seconds.
This helped me and others.
Please read in this threat: http://forum.xda-developers.com/showthread.php?t=1831161
Click to expand...
Click to collapse
But I have no recovery anymore. The cwm replaced the "normal" recovery.
Ottilooping said:
But I have no recovery anymore. The cwm replaced the "normal" recovery.
Click to expand...
Click to collapse
Send me an photo from your "recovery"...
tpauli said:
Send me an photo from your "recovery"...
Click to expand...
Click to collapse
https://www.dropbox.com/s/xl9fx8rb8bpqgkf/IMG_20130212_110830.jpg
Here is the photo.
I was thinking about 2 possible solutions right now.
1. get another nandroid backup (Problem didnt see any for the 16gb WE version)
2. try no reflash another CWM version or maybe ventana cwm and try again to flash Cyanogen (don't know if its possible to just flash another recovery as an image with the current working recovery)
So what do you guys think?
Ottilooping -
You were running ICS before flashing to CM, right?
da_reeseboy said:
Ottilooping -
You were running ICS before flashing to CM, right?
Click to expand...
Click to collapse
Yes, thats correct.
Ottilooping said:
https://www.dropbox.com/s/xl9fx8rb8bpqgkf/IMG_20130212_110830.jpg
Here is the photo.
I was thinking about 2 possible solutions right now.
1. get another nandroid backup (Problem didnt see any for the 16gb WE version)
2. try no reflash another CWM version or maybe ventana cwm and try again to flash Cyanogen (don't know if its possible to just flash another recovery as an image with the current working recovery)
So what do you guys think?
Click to expand...
Click to collapse
That looks good!
My suggestion: Flash the formatdata.zip and than install the last v0.9.2 from koshu located here: http://forum.xda-developers.com/showthread.php?t=1846044
I was coming from ics too.
Problem solved. CM is running. Thanks for your help, exspecialy to you tpauli.
The formatdata.zip was the key
One last question. I am using the folio keyboard with an european layout (qwertz), but with Cyanogen it is us layout (qwerty). How can I change this?

Is this brick situation? -HELP-

Here is the newbie situation.
1)i just root my N4 JWR66Y successfully then
2)Flash a custom rom and reboot successfully
3)was playing around the new roms n reboot THEN this happen
4)it bootloop and i power off the phone then it comes to TWRP 2.6.0
5)try to reboot and there is no OS install
6)i still able to boot into recovery and bootloader but cant BOOT
Please help me guys:crying:
Just flash the ROM again.
Sent from my GT-P3100 using xda app-developers app
If you can get to the bootloader/recovery you're not bricked.
The moment you can't do anything with your phone except throw it at somebody is the moment its bricked. You are ok my friend as posted above just flash another rom but I am confused if your phone would only go into recovery why would you not try and restore backup or just flash another rom?
Edit: Hopefully you made a backup of your original rom? Also what recovery are you using
playya said:
The moment you can't do anything with your phone except throw it at somebody is the moment its bricked. You are ok my friend as posted above just flash another rom but I am confused if your phone would only go into recovery why would you not try and restore backup or just flash another rom?
Edit: Hopefully you made a backup of your original rom? Also what recovery are you using
Click to expand...
Click to collapse
:good:so its not bricked. nothing is inside the storage so do my backup file.it seems the internal memory is EMPTY.
SOLVED heres the guide http://forum.xda-developers.com/showthread.php?t=2376681
Thanks guys for replying

Flashed ROM in TWRP - custom recovery + root gone?

I just flashed a 802d stock ROM through TWRP 2.7 (AutoRec). I started out by wiping dalvik cache, cache and data. I then pressed Install and found the zip and installed that. After it was done, I did a dalvik + cache wipe again just to be safe (It asked if I wanted and I complied). Rebooted into system. It was quite buggy to begin with, so I wanted to try re-flashing, but it looks like my custom recovery has disappeared. I assume my root access went with it.
Everytime I try to get into recovery. It doesn't show the TWRP recovery, but merely ask if I want to factory reset my phone.
Currently, I'm downloading a clean kdz of the 802d ROM (it's taking a while) and aim to start all over with rooting and installing custom recovery and re-installing apps, but if anyone has a different solution, it would be most welcome. I'm quite the noob here. I thought TWRP would be fool-proof and would therefore allow me to restore a backup at any time. But currently, that does not appear to be the case.
Please do prove me wrong
Depends on what custom rom you were installing.
Trixanity said:
I just flashed a 802d stock ROM through TWRP 2.7 (AutoRec). I started out by wiping dalvik cache, cache and data. I then pressed Install and found the zip and installed that. After it was done, I did a dalvik + cache wipe again just to be safe (It asked if I wanted and I complied). Rebooted into system. It was quite buggy to begin with, so I wanted to try re-flashing, but it looks like my custom recovery has disappeared. I assume my root access went with it.
Everytime I try to get into recovery. It doesn't show the TWRP recovery, but merely ask if I want to factory reset my phone.
Currently, I'm downloading a clean kdz of the 802d ROM (it's taking a while) and aim to start all over with rooting and installing custom recovery and re-installing apps, but if anyone has a different solution, it would be most welcome. I'm quite the noob here. I thought TWRP would be fool-proof and would therefore allow me to restore a backup at any time. But currently, that does not appear to be the case.
Please do prove me wrong
Click to expand...
Click to collapse
Ok first if you really do have custom recovery in the factory reset screen clicking the power button three times will boot you into recovery, if you can boot into the Rom then download a root checker app to check if you still have root
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
XxZombiePikachu said:
Ok first if you really do have custom recovery in the factory reset screen clicking the power button three times will boot you into recovery, if you can boot into the Rom then download a root checker app to check if you still have root
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2736854 <- this is the ROM I flashed. It's a stock ROM containing the latest d firmware for the D802.
I just checked for root access - it's not there anymore. I will try to boot into recovery now through the method you suggested. I'll edit my post with the results.
Edit: Your method worked My recovery is there. Great! I thought it would boot straight into recovery, so the factory reset option mislead me. Now, I have to ask: did I do anything wrong in my flashing? For example. In the Mount section, only Data and Cache is mounted. Should system be mounted or is it irrelavant? Is there anything in particular I need to do in Wipe? I merely pressed Advanced Wipe and seleceted Dalvik Cache, Data and Cache and swiped to wipe. That's it.
Trixanity said:
http://forum.xda-developers.com/showthread.php?t=2736854 <- this is the ROM I flashed. It's a stock ROM containing the latest d firmware for the D802.
I just checked for root access - it's not there anymore. I will try to boot into recovery now through the method you suggested. I'll edit my post with the results.
Click to expand...
Click to collapse
well if you would have noticed in the install process it states to flash supersu after flashing the rom
XxZombiePikachu said:
well if you would have noticed in the install process it states to flash supersu after flashing the rom
Click to expand...
Click to collapse
Yeah, I did read that. This might sound stupid, but I figured that the listed SuperSU update was meant for people with an older version of SuperSU as in making sure to have the latest version of SuperSU, since I already had the latest version, I neglected to do that step. My bad. I will copy the zip in question to my phone and try re-flash both zips and see what happens. At least I have my backups to fall back on.
Another dumb question if you will. Since I didn't wipe any of my data. My apps are still present in the file system, but they are not installed nor do they have market links. Is there a way to install them or should I try to recover them through Titanium Backup? Or is it easier to simply wipe the data as well and use Titanium Backup to restore my apps?
Trixanity said:
Another dumb question if you will. Since I didn't wipe any of my data. My apps are still present in the file system, but they are not installed nor do they have market links. Is there a way to install them or should I try to recover them through Titanium Backup? Or is it easier to simply wipe the data as well and use Titanium Backup to restore my apps?
Click to expand...
Click to collapse
I think you should wipe and restore from tibu since there isn't a guarantee that redownloading your apps from the playstore will keep there old data
Thank you so much for taking your time to answer my questions. The second flash seemed succesful, but it didn't fix my biggest reason for flashing the ROM in the first place: the hissing audio bug. So I'll just try to do a restore of my latest backup and I'll make do with my temporary fix that actually works.
While it may seem to that I have wasted everyone's time, I think I've learned some valuable lessons, so I don't think it was entirely a bad thing
Hopefully, my restore will be succesful
Trixanity said:
Thank you so much for taking your time to answer my questions. The second flash seemed succesful, but it didn't fix my biggest reason for flashing the ROM in the first place: the hissing audio bug. So I'll just try to do a restore of my latest backup and I'll make do with my temporary fix that actually works.
While it may seem to that I have wasted everyone's time, I think I've learned some valuable lessons, so I don't think it was entirely a bad thing
Hopefully, my restore will be succesful
Click to expand...
Click to collapse
just in case since you don't mention the fix, I know the kk audio bug has a fix with g2tweaksbox over in the faq of first post it explains what needs to be done
XxZombiePikachu said:
just in case since you don't mention the fix, I know the kk audio bug has a fix with g2tweaksbox over in the faq of first post it explains what needs to be done
Click to expand...
Click to collapse
I did try that fix. It didn't remove the hiss entirely for me. Maybe removed 50% of the hiss, but I've heard of it working 100% for a lot of people. I've been using the ELT > Audio Loopback test from the hidden menu. It removes the hiss by about 99%. Only annoying thing is that I need to do it on every reboot which is why I wanted a more permanent fix.
Seems like my restore has caused a bootloop. Everything went accordingly, except the installation of SuperSU afterwards. Kept saying it failed to copy to the system folder despite system being mounted. The bootloop started when trying to boot into system after restore + failed SuperSU installation.
Edit: Fixed the SuperSU failure to install by wiping dalvik etc. but bootloop persists. I somewhat assume this is because the restore function doesn't work when the current ROM is different from the ROM the backup was made with? The backup was made with D802 20b firmware and the current ROM which is the one I flashed was the D802 20d firmware. Am I on to something?
Trixanity said:
I did try that fix. It didn't remove the hiss entirely for me. Maybe removed 50% of the hiss, but I've heard of it working 100% for a lot of people. I've been using the ELT > Audio Loopback test from the hidden menu. It removes the hiss by about 99%. Only annoying thing is that I need to do it on every reboot which is why I wanted a more permanent fix.
Seems like my restore has caused a bootloop. Everything went accordingly, except the installation of SuperSU afterwards. Kept saying it failed to copy to the system folder despite system being mounted. The bootloop started when trying to boot into system after restore + failed SuperSU installation.
Edit: Fixed the SuperSU failure to install by wiping dalvik etc. but bootloop persists. I somewhat assume this is because the restore function doesn't work when the current ROM is different from the ROM the backup was made with? The backup was made with D802 20b firmware and the current ROM which is the one I flashed was the D802 20d firmware. Am I on to something?
Click to expand...
Click to collapse
A backup restore should always work whether different versions or not, are you able to get into download mode?have you tried kdz to stock?
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
XxZombiePikachu said:
A backup restore should always work whether different versions or not, are you able to get into download mode?have you tried kdz to stock?
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
Click to expand...
Click to collapse
I just fixed it by going into recovery and flashing the D802 20d firmware again. It'll do for now. Honestly don't know why the restore from backup didn't work. Either the backup was corrupt or I've done something wrong.
I did restore my apps (so far) flawlessly and the rom does appear to perform similarly to my older firmware. Plus there's added features such as knock code so it's not all bad.
I do have a D802 20d kdz firmware available on my computer in case I want to go completely stock and/or start over. But I'll give this one a try over the next few days and see whether I'll keep this.
Trixanity said:
I just fixed it by going into recovery and flashing the D802 20d firmware again. It'll do for now. Honestly don't know why the restore from backup didn't work. Either the backup was corrupt or I've done something wrong.
I did restore my apps (so far) flawlessly and the rom does appear to perform similarly to my older firmware. Plus there's added features such as knock code so it's not all bad.
I do have a D802 20d kdz firmware available on my computer in case I want to go completely stock and/or start over. But I'll give this one a try over the next few days and see whether I'll keep this.
Click to expand...
Click to collapse
yea I'm still waiting for that knock code update on my g2, times like these make you hate being with carriers

Did I bricked My Yoga Book YB1-X90L

:crying: My device boots in CHERRYVIEW D1 PALTFORM/INTEL (CHTTYETI.X64************) ((something like Windows BIOS??)
And that all.
I tried Platform Flash Tool Lite but missing flash.xml file. but even I am not sure it will work...
any advice or other solution please....
mmusaad said:
:crying: My device boots in CHERRYVIEW D1 PALTFORM/INTEL (CHTTYETI.X64************) ((something like Windows BIOS??)
And that all.
I tried Platform Flash Tool Lite but missing flash.xml file. but even I am not sure it will work...
any advice or other solution please....
Click to expand...
Click to collapse
what did you flash and what did you exactly do?
Hi
I have twrp backup..
I wiped everything using twrp...
Then restore my backup..
in restoring option I had two bootloaders I removed first bootloader and used the second bootloader..
Also I removed data backup...
Then it start to load only bios screen
mmusaad said:
I have twrp backup..
I wiped everything using twrp...
Then restore my backup..
in restoring option I had two bootloaders I removed first bootloader and used the second bootloader..
Also I removed data backup...
Then it start to load only bios screen
Click to expand...
Click to collapse
shouldn't have done that...think the bootloader you removed is the android one, while the other one might be the bios.
here is a link to some rom with flashfiles....i can't tell you how to flash because all the instructions are in chinese. there are different flashfiles, which peform different ways of flashing the system, eg. without deleting data, or without updating the bootloader.
maybe it's 'flash_factory_update_pos_bootloader' - my guess it only updates the bootloader partitions...if it works and you have a bootloader again you could probably load recovery again and restore your system / data.
(you might use 'flash factory 1st stage' and ' flash factory 2nd stage' as well (i think those flash the whole system again, but I'm not sure. it's just a guess.)
hope you will manage it
look at the flash_guide.docx, it's in chinese but with google translator you can get some information about it.
to use the flash tool i think you must boot into dnx fastboot mode...hold 'volume up' + 'volume down' + 'power' to get into dnx mode (yes, pressing vol up and vol down at the same time works!)
maybe
Hi
danjac said:
shouldn't have done that...think the bootloader you removed is the android one, while the other one might be the bios.
here is a link to some rom with flashfiles....i can't tell you how to flash because all the instructions are in chinese. there are different flashfiles, which peform different ways of flashing the system, eg. without deleting data, or without updating the bootloader.
maybe it's 'flash_factory_update_pos_bootloader' - my guess it only updates the bootloader partitions...if it works and you have a bootloader again you could probably load recovery again and restore your system / data.
(you might use 'flash factory 1st stage' and ' flash factory 2nd stage' as well (i think those flash the whole system again, but I'm not sure. it's just a guess.)
hope you will manage it
look at the flash_guide.docx, it's in chinese but with google translator you can get some information about it.
to use the flash tool i think you must boot into dnx fastboot mode...hold 'volume up' + 'volume down' + 'power' to get into dnx mode (yes, pressing vol up and vol down at the same time works!)
maybe
Click to expand...
Click to collapse
Thanks hope it will work.
if you have an alternative download link as this link is really slow...
mmusaad said:
Thanks hope it will work.
if you have an alternative download link as this link is really slow...
Click to expand...
Click to collapse
not at the moment...
can you once more explain in detail what you did and how you ended up having no bootloader anymore.
i'm still trying to figure out how you were left with no bootloader (can you post a picture of that ?bios?).
i just want to know whether this is somehow related to the ported twrp. from my knowledge there's no way to wipe the bootloader or whatever.
thx in advance
Hi
First thanks I used Platform Flash Tool Lite downloaded from intel website and flash the file it complete 75% but then faild. However it started on logo screen where I immediately but it in dxn mode and booted twrp and it worked. Still WIP. I will update you of the outcome.
As for how it happened... as I mentioned earlier I wiped everything using twrp and selected advice option where you select cache, system, internal memory, etc...
And restore twrp earlier backup but I modified the backup data stored in my pc it had bootloader and bootloader1.. then I removed first bootloader and renamed bootloader1 to bootloader. During twrp restoration process, twrp read my backup and shown me the folders that will be restored, there I noticed that I succeeded on having only one bootloader and also unchecked the data folder and restored it. Where it ended on attached screen...
mmusaad said:
First thanks I used Platform Flash Tool Lite downloaded from intel website and flash the file it complete 75% but then faild. However it started on logo screen where I immediately but it in dxn mode and booted twrp and it worked. Still WIP. I will update you of the outcome.
As for how it happened... as I mentioned earlier I wiped everything using twrp and selected advice option where you select cache, system, internal memory, etc...
And restore twrp earlier backup but I modified the backup data stored in my pc it had bootloader and bootloader1.. then I removed first bootloader and renamed bootloader1 to bootloader. During twrp restoration process, twrp read my backup and shown me the folders that will be restored, there I noticed that I succeeded on having only one bootloader and also unchecked the data folder and restored it. Where it ended on attached screen...
Click to expand...
Click to collapse
if you can access twrp again, just restore your backup as it is...all partitions without changing anything.
good luck. hope it works.
now people know how to get to the bios/bootmanager (maybe it helps for dual boot)
do you know what options there were, something like boot from sdcard/otg (usb) etc...?
Hi
There where two options
Android IA
EFI Hard Disk
As for my issue I was able to boot twrp and restore my backup..
But it seems I played around bios screen which ended up not showing bootloader or recover option even bios....
It's feel like something running but not showing in the scteen. Is there any way to reset bios or a stock rom to restore the device like out-of-box status....
Hi
mmusaad said:
There where two options
Android IA
EFI Hard Disk
As for my issue I was able to boot twrp and restore my backup..
But it seems I played around bios screen which ended up not showing bootloader or recover option even bios....
It's feel like something running but not showing in the scteen. Is there any way to reset bios or a stock rom to restore the device like out-of-box status....
Click to expand...
Click to collapse
I found out that it was running through HDMI output in the initial boot and it will not show in the tablet screen..
I did it again with bootloader modification and got the BOIS mode and connecting my tablet to LED TV through HDMI output I managed to reset the bios and got it back to normal (know boot showing in my tablet screen...)
When i flash the file you share and used flash/blank setting it will reach 80 to 85% but fail in bootloader flashing. then i used DXN mode and fastboot flash twrp recovery it will bring the main service options where I did factory reset then it will start loading with little screen corruption. however it will load perfectly after couple of reboots but without the Halo Keyboard. i could not find out how to enable it...
Then i used my TWRP backup and restore it where everything working fine....
My request is it possible to modify the flash-able file you send to load a perfect stock rom. it will help many people as it will be easy to use with Intel android flash tool...???
Thanks mmusaad and danjac, glad that you unbricked it.
Can I ask how does one flash it with Platform Flash Tool Lite? I failed to infer the meaning of 'setup your board' from intel's description:
> You have already set up your board and connected the board to your host system. This includes assembling your board, installing the appropriate drivers, and flashing your firmware.
(I'm trying to run or install Linux on yogabook, which I feel may brick it a few times.)
Also, do you think one can enter the BIOS setting or boot device selection without bricking it first?
thanks
Hi
momocraft said:
Thanks mmusaad and danjac, glad that you unbricked it.
Can I ask how does one flash it with Platform Flash Tool Lite? I failed to infer the meaning of 'setup your board' from intel's description:
> You have already set up your board and connected the board to your host system. This includes assembling your board, installing the appropriate drivers, and flashing your firmware.
(I'm trying to run or install Linux on yogabook, which I feel may brick it a few times.)
Also, do you think one can enter the BIOS setting or boot device selection without bricking it first?
thanks
Click to expand...
Click to collapse
Try installing this file it suppose boot correctly...
https://software.intel.com/system/files/managed/1e/e8/IntelAndroidDrvSetup1.10.0.zip
mmusaad said:
Try installing this file it suppose boot correctly...
https://software.intel.com/system/files/managed/1e/e8/IntelAndroidDrvSetup1.10.0.zip
Click to expand...
Click to collapse
Thanks, I was able to flash with FlashToolLite (linux). The only problem is that my halo keyboard stopped working (maybe rom dismatch? My yogabook is from japan).
Anyway thanks /o\
momocraft said:
Thanks, I was able to flash with FlashToolLite (linux). The only problem is that my halo keyboard stopped working (maybe rom dismatch? My yogabook is from japan).
Anyway thanks /o\
Click to expand...
Click to collapse
Did you have any TWRP backup.?
I have faced the same issue the solution was to restore boot & country img. Or one of them....mmmm I forgot...
danjac said:
shouldn't have done that...think the bootloader you removed is the android one, while the other one might be the bios.
here is a link to some rom with flashfiles....i can't tell you how to flash because all the instructions are in chinese. there are different flashfiles, which peform different ways of flashing the system, eg. without deleting data, or without updating the bootloader.
Click to expand...
Click to collapse
Greetings to all.
 @danjac: Could you provide a link to a YB1-X90F ROM? I would like to try flashing it on a chinese version model. @mmusaad: please excuse my irrelevant to the subject request.
mmusaad said:
First thanks I used Platform Flash Tool Lite downloaded from intel website and flash the file it complete 75% but then faild. However it started on logo screen where I immediately but it in dxn mode and booted twrp and it worked. Still WIP. I will update you of the outcome.
As for how it happened... as I mentioned earlier I wiped everything using twrp and selected advice option where you select cache, system, internal memory, etc...
And restore twrp earlier backup but I modified the backup data stored in my pc it had bootloader and bootloader1.. then I removed first bootloader and renamed bootloader1 to bootloader. During twrp restoration process, twrp read my backup and shown me the folders that will be restored, there I noticed that I succeeded on having only one bootloader and also unchecked the data folder and restored it. Where it ended on attached screen...
Click to expand...
Click to collapse
wow , how did you manage to get into bios and boot from usb ? , i want it too
you can explain how did you get that bios image ? , i have rooted my device , and want to trying to install a stable linux system that will works with the yoga book , i got the yoga book android version
sagi232123 said:
wow , how did you manage to get into bios and boot from usb ? , i want it too
you can explain how did you get that bios image ? , i have rooted my device , and want to trying to install a stable linux system that will works with the yoga book , i got the yoga book android version
Click to expand...
Click to collapse
What you ask for was only a few clicks away my friend:
https://forum.xda-developers.com/yoga-book/how-to/yoga-book-gnuroot-debian-t3580358
sagi232123 said:
wow , how did you manage to get into bios and boot from usb ? , i want it too
you can explain how did you get that bios image ? , i have rooted my device , and want to trying to install a stable linux system that will works with the yoga book , i got the yoga book android version
Click to expand...
Click to collapse
Hi sagi232123,
I will explain it to you in detail.
I taken a full backup using twrp.
Then I notice two bootloaders.
First named bootloader. "note: I don't remember the full file name."
Second named bootloader1.
I removed bootloader.
Renamed bootloader1 to bootloader using my PC.
Then restored using twrp again, I restored it fully.
Here I was shocked when it load the bios.
Do it and it should do the same.
nan0s7 said:
What you ask for was only a few clicks away my friend:
https://forum.xda-developers.com/yoga-book/how-to/yoga-book-gnuroot-debian-t3580358
Click to expand...
Click to collapse
this is diffrent , running linux through android , i want to run from bios without android
https://forum.xda-developers.com/yoga-book/how-to/boot-bios-how-to-android-t3593340
this is the tut
Hello, I also had a brick problem. I managed to flash the firmware of 270916 then the OTAs until the last of April 28th. All works fine, Halo keyboard, wifi etc but the problem is that tablet no longer recognizes the sim card! Om settings the Sim option are greyed. Any help?

Categories

Resources