For those that are impatient, didn't want to register for the OTA, or are just curious:
http://ota-downloads.nvidia.com/ota...dd-full_ota-41937_664.8257.20160212074447.zip
Enjoy
How is it?
ahoslc said:
How is it?
Click to expand...
Click to collapse
dunno, I only got to initiate the update, capture the url, and had to leave to go back to work.
Need the 16gb one
How do you even become part of the Dev Preview? Anyone get the same for the 16GB?
I just got home from work, and finished up the install process. So far everything looks the same, but my box is more responsive. Prior to the update my 500GB unit kept getting delays when selecting stuff off the homescreen. If I scrolled all the way right on the top bar, the end items would pixelate, then if I scrolled all the way back, the beginning icons would be pixelated now. Not too long ago I did a factory reset w/ wipe, and it was a lot better, but came back over time. I was getting ready to RMA it. So far that is gone. I'll know more if my issues are 100% gone with more time and use.
edit: CEC volume control w/ nvidia remote is fixed
Luxferro said:
edit: CEC volume control w/ nvidia remote is fixed
Click to expand...
Click to collapse
:victory:
Need one for the 16GB version.
just remember if you have the 500gb version that theres a bug that after you flash it'll only show 11gb free.to fix you have to do a factory reset, which takes forever.
How do we apply the file?...
Do we just flash it from twrp recovery environment?...
Luxferro said:
edit: CEC volume control w/ nvidia remote is fixed
Click to expand...
Click to collapse
This mean remote touchpad works?
If someone could grab the 16gb link it would be appreciated.
How to safe apply this update? I have 2.1 rooted and custom twrp installed!
Izsūtīts no manas Nokia 3310 используя бесплатную xda app
visitor29 said:
How to safe apply this update? I have 2.1 rooted and custom twrp installed!
Izsūtīts no manas Nokia 3310 используя бесплатную xda app
Click to expand...
Click to collapse
If it were me Id make a twrp backup and try and install the zip via twrp.
alright
did update via twrp after and before reboot system clean dalvik / cash
all works (didnt brick or kind of call how to boot in recovery or etc...all startdet normaly)
about controller touch pad button - for me...same as before (and yes i did controller and remote update .... less then five minutes takes me, so be patient) or maybe i don't know something where or in which application need use that...
after updating - twrp and root will be gone and twrp from previus 2.1 wil not gonna work tooo (already checked)
There is a similar problem on the Shield Tablet. The new bootloader won't boot older kernels. I expect that to be the same problem with twrp here. I can probably hack something together, but I don't want to release anything based off a leak. I am working on stuff internally, though. Once the official update and source drops, I should be able to get a new twrp out the door pretty quickly.
Question for those already booting the new ota: can you get to the bootloader screen by holding the power button and plugging in the power cable? Also, does fastboot boot do anything other than hang the device?
Steel01 said:
There is a similar problem on the Shield Tablet. The new bootloader won't boot older kernels. I expect that to be the same problem with twrp here. I can probably hack something together, but I don't want to release anything based off a leak. I am working on stuff internally, though. Once the official update and source drops, I should be able to get a new twrp out the door pretty quickly.
Question for those already booting the new ota: can you get to the bootloader screen by holding the power button and plugging in the power cable? Also, does fastboot boot do anything other than hang the device?
Click to expand...
Click to collapse
Yeah working without lag if following by this
https://m.youtube.com/watch?v=2AzHF-uNiY8
I don't really understand your 2nd question?!
Fastboot commands from cmd didn't give me trouble with booting, rebooting if you about this...generally was all ok
Previous twrp from 2.1 boots up only picture was upside-down...well and wired mouse didn't responded
Izsūtīts no manas Nokia 3310 используя бесплатную xda app
visitor29 said:
Yeah working without lag if following by this
https://m.youtube.com/watch?v=2AzHF-uNiY8
I don't really understand your 2nd question?!
Fastboot commands from cmd didn't give me trouble with booting, rebooting if you about this...generally was all ok
Previous twrp from 2.1 boots up only picture was upside-down...well and wired mouse didn't responded
Izsūtīts no manas Nokia 3310 используя бесплатную xda app
Click to expand...
Click to collapse
He wants to know if the boot (vs flash) command of fastboot works properly now. It was broken last release.
When you 'fastboot boot boot.img' it will boot that copy instead of flashing it to the device, whereas 'fastboot flash boot boot.img' would flash the boot.img to the boot partition.
Luxferro said:
He wants to know if the boot (vs flash) command of fastboot works properly now. It was broken last release.
When you 'fastboot boot boot.img' it will boot that copy instead of flashing it to the device, whereas 'fastboot flash boot boot.img' would flash the boot.img to the boot partition.
Click to expand...
Click to collapse
https://youtu.be/p_Jeeu_OPC8
Izsūtīts no manas Nokia 3310 используя бесплатную xda app
Luxferro said:
For those that are impatient, didn't want to register for the OTA, or are just curious:
http://ota-downloads.nvidia.com/ota...dd-full_ota-41937_664.8257.20160212074447.zip
Enjoy
Click to expand...
Click to collapse
How did you grab the ota link? Ive signed up for my ota just curious how you would grab the link once it comes.
Related
Hello Members
I need a Official recovery.img dump for this ICS version
ACER_AV041_A100_0.002.00_ww_GEN1 link >>http://vache-android.com/v1/download.php?fileID=116
my recovery does not install update.zip patches and power key does not select any opition
http://youtu.be/CWFlA1W08wE
this is my bootloader version
Bootloader v0.03.11-ICS: Starting Fastboot USB download protocol
help me please
You Can make a backup this IMG with "Acer recovery tool" downloaded from the google play store
thanks
Ill attach the stock recovery for one of the ICS roms that vache posted, but I can't remember the exact build #. I know it's not the leak version, and if it helps I also used it to flash back to stock after some funny business.
I just noticed something, you are aware that image you linked to is a A101 image, right?
masr1979 said:
Ill attach the stock recovery for one of the ICS roms that vache posted, but I can't remember the exact build #. I know it's not the leak version, and if it helps I also used it to flash back to stock after some funny business.
Click to expand...
Click to collapse
thanks now works
u save my tab
rollidark said:
thanks now works
u save my tab
Click to expand...
Click to collapse
I'm glad it worked out for you, but if this fixed your device that you made a previous bricked thread about, could you please to back, and post an update to that thread discribing what you did, and how you did it, to get the device back up again? It'll definatly help anyone else with this same issue.
You're welcomed, we are here to help each other after all. You should follow pio's advice and describe what you did so others can benefit from your experience. We have to make such info as readily available as possible.
Having the same issue described
I have a locked bootloader tried many different A100 update.zip files. Please tell me how you fixed it with the recovery image I have the locked bootloader v 0.03 up.
citricube said:
I have a locked bootloader tried many different A100 update.zip files. Please tell me how you fixed it with the recovery image I have the locked bootloader v 0.03 up.
Click to expand...
Click to collapse
He had a brick not a locked bootloader, you can't flash a bootloader directly if its locked with fast boot.
Tapatalked from my Galaxy S II.
Awesome
Looks like my tablet is going back to Acer Repair for the second time in about a month. :cyclops:
citricube said:
Looks like my tablet is going back to Acer Repair for the second time in about a month. :cyclops:
Click to expand...
Click to collapse
Wow that's a pretty bad run, what's wrong with either one?
Yes I know holy threadjack Batman
Tapatalked from my Galaxy S II.
masr1979 said:
Ill attach the stock recovery for one of the ICS roms that vache posted, but I can't remember the exact build #. I know it's not the leak version, and if it helps I also used it to flash back to stock after some funny business.
Click to expand...
Click to collapse
Hi, I have the same problem as rollidark. What do you do with this recovery image. It seems rollidark used it to fix his issue.
thanks
liltyke said:
Hi, I have the same problem as rollidark. What do you do with this recovery image. It seems rollidark used it to fix his issue.
thanks
Click to expand...
Click to collapse
Put an stock rom update on the root of your external sdcard (vache & zeronull have released some), rename it update.zip. I'd don't recommend recommend relocking your bootloader unless you're absolutely sure what you are doing, so that means that if the rom you downloaded has a bootloader.blob you need to delete it, or look for one that doesn't have it (I think vache's don't have it)
Now reboot into fastboot
adb reboot bootloader
Click to expand...
Click to collapse
once in fastboot
fastboot erase recovery
Click to expand...
Click to collapse
then
fastboot flash recovery "recovery.img file location"
Click to expand...
Click to collapse
That should give you stock recovery, after that I usually hold down the volume button closest to the lock switch and run
fastboot reboot
Click to expand...
Click to collapse
After you see the green android with the progress bar in the bottom your rom should be flashing, and hopefully once finished you'll be ready to re-root, and reflash your rom... if you were careful and had a nandroid-backup you could even restore your /data (I don't usually restore my /system or other partitions).
Godspeed in your flashing endeavors my friend.
masr1979 said:
Put an stock rom update on the root of your external sdcard (vache & zeronull have released some), rename it update.zip. I'd don't recommend recommend relocking your bootloader unless you're absolutely sure what you are doing, so that means that if the rom you downloaded has a bootloader.blob you need to delete it, or look for one that doesn't have it (I think vache's don't have it)
Now reboot into fastboot
once in fastboot
then
That should give you stock recovery, after that I usually hold down the volume button closest to the lock switch and run
After you see the green android with the progress bar in the bottom your rom should be flashing, and hopefully once finished you'll be ready to re-root, and reflash your rom... if you were careful and had a nandroid-backup you could even restore your /data (I don't usually restore my /system or other partitions).
Godspeed in your flashing endeavors my friend.
Click to expand...
Click to collapse
Nicely done, masr1979!:good:
masr1979 said:
Put an stock rom update on the root of your external sdcard (vache & zeronull have released some), rename it update.zip. I'd don't recommend recommend relocking your bootloader unless you're absolutely sure what you are doing, so that means that if the rom you downloaded has a bootloader.blob you need to delete it, or look for one that doesn't have it (I think vache's don't have it)
Now reboot into fastboot
once in fastboot
then
That should give you stock recovery, after that I usually hold down the volume button closest to the lock switch and run
After you see the green android with the progress bar in the bottom your rom should be flashing, and hopefully once finished you'll be ready to re-root, and reflash your rom... if you were careful and had a nandroid-backup you could even restore your /data (I don't usually restore my /system or other partitions).
Godspeed in your flashing endeavors my friend.
Click to expand...
Click to collapse
thank you very much for the detailed explanation masr1979. I'll give it a shot when I get home from work.
Basically I got the rear camera replaced, it was working great. About a couple weeks later It's running sluggishly because I was running too many apps at once. So I decided to press the reset button while It was lagging out, next thing I know It's stuck at the silver android logo forever. I tried using some update.zip's but that just made the problem worse.
Well it seems my knowledge level was a few steps back from where it needed to be to fully understand the instructions as posted, so the last 24 hours have been a whole lot of 'old dog learning new tricks'. I have adb and fastboot installed now via one of the threads found through googling. When I enter 'adb reboot bootloader' everything seems to go fine, but when I enter 'fastboot erase recovery' I get 'ersaing 'recovery' ... FAILED (remote: (00000002)) ANy tips from you pros?? I've been beating my head against the wall for a while and neither my head or the wall are looking too good right now Thanks for any help anyone may offer.
liltyke said:
Well it seems my knowledge level was a few steps back from where it needed to be to fully understand the instructions as posted, so the last 24 hours have been a whole lot of 'old dog learning new tricks'. I have adb and fastboot installed now via one of the threads found through googling. When I enter 'adb reboot bootloader' everything seems to go fine, but when I enter 'fastboot erase recovery' I get 'ersaing 'recovery' ... FAILED (remote: (00000002)) ANy tips from you pros?? I've been beating my head against the wall for a while and neither my head or the wall are looking too good right now Thanks for any help anyone may offer.
Click to expand...
Click to collapse
Need a little more information first.
What android version are you on now? What boot loader version does it show upper left on boot? What all have you done to this point?
Tapatalked from my Galaxy S II.
pio_masaki said:
Need a little more information first.
What android version are you on now? What boot loader version does it show upper left on boot? What all have you done to this point?
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
Thanks for jumping in here pio_masaki. It's very much appreciated.
Sorry for the lack of details, I realize that I should have given that info from in my first post.
Android version is 4.0.3 ,I flashed it with the first ICS leak that showed up here on XDA.
Bootloader version is v0-03.11-ICS
The A100 is not rooted.
After the official ICS update was being streamed I realized that I wasn't getting it. Figured it was because I had already flashed the early leak. I saw here on XDA a few threads where people were trying to get back to HC because they were having the same problem. I followed steps and advice listed in those other threads but nothing was working for me. I always got the dead android logo any time I tried to recover using an 'update.zip' on my external sd card. When I get the dead android logo and press the home button I do get the recovery menu button soon noticed that even though I could scroll through the menu I could not select any of the options. I saw this thread and it seemed to be very similar to my situation.
thanks again for your time.
liltyke said:
Thanks for jumping in here pio_masaki. It's very much appreciated.
Sorry for the lack of details, I realize that I should have given that info from in my first post.
Android version is 4.0.3 ,I flashed it with the first ICS leak that showed up here on XDA.
Bootloader version is v0-03.11-ICS
The A100 is not rooted.
After the official ICS update was being streamed I realized that I wasn't getting it. Figured it was because I had already flashed the early leak. I saw here on XDA a few threads where people were trying to get back to HC because they were having the same problem. I followed steps and advice listed in those other threads but nothing was working for me. I always got the dead android logo any time I tried to recover using an 'update.zip' on my external sd card. When I get the dead android logo and press the home button I do get the recovery menu button soon noticed that even though I could scroll through the menu I could not select any of the options. I saw this thread and it seemed to be very similar to my situation.
thanks again for your time.
Click to expand...
Click to collapse
So...you flashed the bootloader to get back to HC and now it won't use update.zip? What about booting into android, does that still work? Or fast boot? Or uhm...I seem to recall having to do a hard reset to get the downgrade to work, have you done this too? I never downgraded just seemed pointless when I was already on ics so I'm not experienced with it, just recall seeing the boot loader needing a hard reset to work.
Tapatalked from my Galaxy S II.
No, I never flashed the bootloader, not unless that happens while trying to run an update.zip. adb and fastboot seem to be working. Based on the earlier instructions 'adb reboot bootloader' does restart the A100 and gives me the bootloader message at the top left of the screen. When I run the ' fastboot erase recovery' command I get the FAILED message in the command prompt window and also get a message in red text on the A100 saying 'Fastboot: not support the command in lockmode, failed to process command erase: recovery error (0x2)'. When I run the 'fastboot reboot' command the A100 does restart. So all that leads to believe that the communication from my computer to the A100 is ok.
Booting into Android. The A100 starts and works fine if that is what you are referring too. As far as the hard reset, if that's the process of holding down the volume button while powering up and flipping the lock switch back and forth to reset the unit, then yes I have done that and it does work. My whole goal here is to get the unit to running ICS legitimately and get updates from ACER. I don't care what I have to do, it's just a couple of the other threads mentioned the need to go back to HC to get the official ICS update. So that's why I tried that. But the last time a update.zip worked was when I flashed the leaked ICS. I have got the dead android logo every time since.
Sorry if some of this info is redundant from my earlier post, I just wanted to get it all in the same place.
Thanks again for your help.
Hi everybody,
I'm so angry with my Nexus 7 (wifi 2013) because I just made it mess up.
Let me tell you how stupid I was.
First, I tried to root but it failed.
Second, I used 'Back to Stock' with 'Nexus Root Toolkit v1.7.2'. Finally, I got stuck at Google logo
I tried some solutions on the internet but it still unchanged anything.
Could you show me how to fix it, please?
Thank you so much.
This is the images of error that I got (I'm sorry I cannot insert image because I'm a new member of this forum, could you go to the link below to see more details?)
s1019.photobucket.com/user/namserious/media/Error_Nexus7.png.html
Your /system is broken.
Try restoring factory defaults using this post:
http://forum.xda-developers.com/showthread.php?p=45671279#post45671279
Restoring Successfully
sfhub said:
Your /system is broken.
Try restoring factory defaults using this post:
http://forum.xda-developers.com/showthread.php?p=45671279#post45671279
Click to expand...
Click to collapse
Awesome, sfhub :good: :laugh:
Thank you so much. I have restored successfully.
This is my result
i1019.photobucket.com/albums/af319/namserious/WP_20131018_001.jpg
How did you do that?
namserious said:
Awesome, sfhub :good: :laugh:
Thank you so much. I have restored successfully.
This is my result
i1019.photobucket.com/albums/af319/namserious/WP_20131018_001.jpg
Click to expand...
Click to collapse
Hey namserious,
How did you get it working? Did you use the Mini guide given by sfhub? I'm having the same issues with my nexus 7 (2013). I only used for one day. Restarted on the second day and never got anything after the Google logo. Also, my phone wasn't rooted, so I didn't have developer options turned on and since I can't get into the system, I can't turn it on either. Will that make a difference?
Thanks.
nexussucks said:
Hey namserious,
How did you get it working? Did you use the Mini guide given by sfhub? I'm having the same issues with my nexus 7 (2013). I only used for one day. Restarted on the second day and never got anything after the Google logo. Also, my phone wasn't rooted, so I didn't have developer options turned on and since I can't get into the system, I can't turn it on either. Will that make a difference?
Thanks.
Click to expand...
Click to collapse
If you didn't root the device or do anything else with it, you should be able to get into Recovery Mode and do a factory reset.
https://support.google.com/nexus/answer/2668187?hl=en
Even recovery doesn't work
I'm not able to get into recovery mode. When I select recovery mode, the tablet starts and displays Google logo again and gets stuck there again.
nexussucks said:
I'm not able to get into recovery mode. When I select recovery mode, the tablet starts and displays Google logo again and gets stuck there again.
Click to expand...
Click to collapse
When you get into recovery you will see just the droid and the red triangle. At this screen you will need to push the power button then Vol Up and release. I had to do that about 3 times then I was able to get the menu items. From there I did a factory reset. After that I was good to go. Hope this helps!
Kind Regards,
Rb
RenderBroken said:
When you get into recovery you will see just the droid and the red triangle. At this screen you will need to push the power button then Vol Up and release. I had to do that about 3 times then I was able to get the menu items. From there I did a factory reset. After that I was good to go. Hope this helps!
Kind Regards,
Rb
Click to expand...
Click to collapse
Thanks Rb, But the thing is I don't get the droid and red triangle at all after I select recovery mode. I have tried everything but nothing happens. I still end up with dreadful Google logo. Suddenly I'm beginning to really hate it.
nexussucks said:
Thanks Rb, But the thing is I don't get the droid and red triangle at all after I select recovery mode. I have tried everything but nothing happens. I still end up with dreadful Google logo. Suddenly I'm beginning to really hate it.
Click to expand...
Click to collapse
You could try re-flashing the factory image.
http://forum.xda-developers.com/showthread.php?t=2487757
Latest factory image build is JSS15R
https://developers.google.com/android/nexus/images#razor
nexussucks said:
Thanks Rb, But the thing is I don't get the droid and red triangle at all after I select recovery mode. I have tried everything but nothing happens. I still end up with dreadful Google logo. Suddenly I'm beginning to really hate it.
Click to expand...
Click to collapse
Im sorry, I didnt read correctly. I had issues too restoring back to Stock since my setup was all changed. I had to use these steps. I am going to assume you know how to use fastboot and what it is.
DISCALAIMER! These steps will delete your user data!!!!
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader BOOTLOADER.img
> fastboot reboot-bootloader
> fastboot -w update IMAGE.zip
So after that I was able to get past the google logo but just stuck at the boot logo (Multi Colored X) I then had to get into recovery using the steps I stated above then did a factory reset.
Success
Rb, I just tried your instructions. YOU ARE A SAVIOUR :laugh:. After 2 days of continous troubleshooting, I had given up my hopes and was thinking of returning it. But suddenly after getting used to seeing the Google logo, I just noticed the android robot on the screen. And after a few seconds I saw the welcome screen... Viola.
Thanks man, I really appreciate your help. :good:
nexussucks said:
Rb, I just tried your instructions. YOU ARE A SAVIOUR :laugh:. After 2 days of continous troubleshooting, I had given up my hopes and was thinking of returning it. But suddenly after getting used to seeing the Google logo, I just noticed the android robot on the screen. And after a few seconds I saw the welcome screen... Viola.
Thanks man, I really appreciate your help. :good:
Click to expand...
Click to collapse
Glad to help! The best thing about Nexus devices are the different fail-safes. If the Rom is screwed up you can flash a new one from recovery. If recovery is screwed you flash a new one from the boot loader. If the boot loader is screwed you can flash another from recovery. Also the N7 2013 tablet is the best for the money. I user mine for work. I am a tech admin for a school district and have certain tools located on my desktop (Active Directory, Printer Manager, etc) and I have RDP installed on my N7. Now when I need to reset a password or whatever i can just RDP to my desktop. This tablet has made my life easier and hopefully yours will too now.
Kind Regards
Rb
Name change
RenderBroken said:
Glad to help! The best thing about Nexus devices are the different fail-safes. If the Rom is screwed up you can flash a new one from recovery. If recovery is screwed you flash a new one from the boot loader. If the boot loader is screwed you can flash another from recovery. Also the N7 2013 tablet is the best for the money. I user mine for work. I am a tech admin for a school district and have certain tools located on my desktop (Active Directory, Printer Manager, etc) and I have RDP installed on my N7. Now when I need to reset a password or whatever i can just RDP to my desktop. This tablet has made my life easier and hopefully yours will too now.
Kind Regards
Rb
Click to expand...
Click to collapse
This is my first experience with a Nexus device and I might have judged it in a wrong way. But I think the problem is not the device but the information regarding the latest Nexus devices. Hopefully there will be more workarounds of the new Nexus devices.
I guess I will have to change my username
nexussucks said:
This is my first experience with a Nexus device and I might have judged it in a wrong way. But I think the problem is not the device but the information regarding the latest Nexus devices. Hopefully there will be more workarounds of the new Nexus devices.
I guess I will have to change my username
Click to expand...
Click to collapse
This is the price we pay for the cutting edge. Also , at least for me, this is part of the fun. Now I have a much better understanding of Android than if I did being an avg. user. I was thinking the same about the name change. lol
RenderBroken said:
Glad to help! The best thing about Nexus devices are the different fail-safes. If the Rom is screwed up you can flash a new one from recovery. If recovery is screwed you flash a new one from the boot loader. If the boot loader is screwed you can flash another from recovery. Also the N7 2013 tablet is the best for the money. I user mine for work. I am a tech admin for a school district and have certain tools located on my desktop (Active Directory, Printer Manager, etc) and I have RDP installed on my N7. Now when I need to reset a password or whatever i can just RDP to my desktop. This tablet has made my life easier and hopefully yours will too now.
Kind Regards
Rb
Click to expand...
Click to collapse
Hey, know it's been a little bit but my nexus 7 says no OS in TWRP recovery. I tried flashing it back to stock but it doesn't work. The bootloader is locked and when I try to do anything manually it just hangs on stuff like erasing 'system'/cache etc... in fastboot. I have not been able to find anything to work. And when I try to fastboot oem unlock it gets stuck when i press volume up and power to accept unlocking it. I have tried different cables and another computer. maybe I should try a third computer.. Do you have any suggestions?
RenderBroken said:
Im sorry, I didnt read correctly. I had issues too restoring back to Stock since my setup was all changed. I had to use these steps. I am going to assume you know how to use fastboot and what it is.
DISCALAIMER! These steps will delete your user data!!!!
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader BOOTLOADER.img
> fastboot reboot-bootloader
> fastboot -w update IMAGE.zip
So after that I was able to get past the google logo but just stuck at the boot logo (Multi Colored X) I then had to get into recovery using the steps I stated above then did a factory reset.
Click to expand...
Click to collapse
I know this is an old thread, but I'm having this exact issue. I'm just stuck on the google screen. I can get into the bootloader just fine, but not the recovery. I followed these directions. Flashed the factory image and everything. But I still can't get past the google logo. I've followed every bit of advice I could find on this issue and I can't seem to get it working. Any help would be greatly appreciated!
*bump*
Does anyone know what's going on? I've tried everything I could find. Multiple times. From the suggestions listed here to the WUG kit to this http://forum.xda-developers.com/showthread.php?t=2381582
Nothing is working. I goes through the reflashing successfully. The command prompt says that everything is done. And then it just gets stuck at the Google screen again. I'm at my wits end and have no idea what to try next. I know that because I can get into the bootloader still, there has to be SOMETHING that will work. But I just don't know. Any ideas?
is there a android L Developers Preview flashable zip? thanks
Sent from my Nexus 7 using XDA Free mobile app
Anyone figure out what is causing this? I got a remanufactured 2nd Gen N7 16G yesterday. Updated to 4.4.4 over the air. Then unlocked the bootloader and rooted. Everything went fine. I installed Franco's latest kernel (r17) over stock and all was well. However, this morning, while using the device in the middle of GoW, it rebooted to the Google Screen and froze there. I could boot into the bootloader and have my comp recognize the device, so could ADB and Fastboot, however, I could not get into recovery. (I had installed TWRP 2.7.1.1 when I rooted). Trying to get into recovery would just freeze at the Google Screen.
So, I then tried both manually ADB'ing commands, as well as using Wug's Toolkit, and both methods seemed to complete successfully without error (I was using the latest Razor-Flo 4.4.4 files from Google's Dev Page so it is not an issue where I am using the Gen 1 files for Grouper or anything like that in error), however, neither method allowed me to boot into recovery, and left me at the same place. No matter what I did, I was stuck at that screen. I ended up calling Asus to RMA.
So, while it is not a current issue for me, I am interested to know if anyone has sorted what the root cause is, and whether it is an issue on the hardware side. I am not a complete noob to the N7 (I have 2 Groupers), and have been modding for a few years on Samsungs, and until this morning, have never had a soft brick I could not fix. This time, I gave up.
Same problem here, I have a Deb 32g, it went a little wonky and then rebooted. No amount of flashing and wiping and fastbooting has been able to recovery it. Gets stuck on Google Logo no matter what I do. Can't get recovery. Can't boot past Google. It will do fastboot without errors, but that's the only thing it will do.
This is a rooted boot image for the moto360. It was made by jcase using a dumped image from my device. It has worked fine to root my device, but nobody is responsible if it breaks your device or anything else. Use it at your own risk!
I'm not completely sure about how it works, but it seems to install the su binary to the system partition, and a few other things, so the root is permanent until you remove it somehow.
I booted this image while my watch was in the KGW42N release, rebooted normally and, after a few hours, I received the update to the latest release normally and maintained root. Your experience may vary.
As far as I know, it will also root the newer releases.
This can be flashed from fastboot.
- turn off the watch
- press and hold the power button until you feel the third vibration, display will show "Bootloader version..."
- connect the jig to your watch and secure it so it will not move accidentally.
- connect the USB cable to your computer. Displaty will show "Transfer mode: USB Connected..."
- Launch a terminal session in your computer and issue the commands:
Code:
fastboot boot boot.img
** It's not fastboot flash boot boot.img ** it only needs to be booted, not flashed.
When your device has finished rebooting, you can enter an ADB shell session and type "su", it should show "[email protected]" in the prompt.
If you find something interesting about the workings of this method, please share!
Big thank you to jcase and beaups, it wouldn't have been possible without their help! Visit http://theroot.ninja/
Enjoy.
https://drive.google.com/folderview?id=0BxTLcy78OveNeW5tY180cWFhZ3c&usp=sharing
Code:
md5 for boot.img: 5c0c7e885711d94e707dd7713fce0d57
Please, don't ask about the jig/cable in this thread, I'll make some instructions soon.
To encourage more research and developments, use the donate button on the right! thanks!
Only reason that I cannot root my device
connect the USB cable to your computer.
Click to expand...
Click to collapse
so sad :/
thanks for awesome job btw
MD5? Drive doesn't seem to show them, at least not that I have found.
What can we do with root?
dproldan said:
This is a rooted boot image for the moto360. It was made by jcase using a dumped image from my device. It has worked fine to root my device, but nobody is responsible if it breaks your device or anything else. Use it at your own risk!
I'm not completely sure about how it works, but it seems to install the su binary to the system partition, and a few other things, so the root is permanent until you remove it somehow.
I booted this image while my watch was in the KGW42N release, rebooted normally and, after a few hours, I received the update to the latest release normally and maintained root. Your experience may vary.
As far as I know, it will also root the newer releases.
This can be flashed from fastboot.
- turn off the watch
- press and hold the power button until you feel the third vibration, display will show "Bootloader version..."
- connect the jig to your watch and secure it so it will not move accidentally.
- connect the USB cable to your computer. Displaty will show "Transfer mode: USB Connected..."
- Launch a terminal session in your computer and issue the commands:
Code:
fastboot boot boot.img
** It's not fastboot flash boot boot.img ** it only needs to be booted, not flashed.
When your device has finished rebooting, you can enter an ADB shell session and type "su", it should show "[email protected]" in the prompt.
If you find something interesting about the workings of this method, please share!
Big thank you to jcase and beaups, it wouldn't have been possible without their help! Visit http://theroot.ninja/
Enjoy.
https://drive.google.com/folderview?id=0BxTLcy78OveNeW5tY180cWFhZ3c&usp=sharing
Code:
md5 for boot.img: 5c0c7e885711d94e707dd7713fce0d57
Please, don't ask about the jig/cable in this thread, I'll make some instructions soon.
Click to expand...
Click to collapse
If you like, I can provide hosting so that it doesn't kill your google drive. If that's OK with you, I can put it up on 2 diff hostings with unlimited bw and great speeds.
Please sell me a "jig". Or at least, show me a detailed guide on how to make one and where to buy parts.
---------- Post added at 02:41 AM ---------- Previous post was at 02:39 AM ----------
trevorftard said:
Please sell me a "jig". Or at least, show me a detailed guide on how to make one and where to buy parts.
Click to expand...
Click to collapse
I apologize. I literally read what you wrote at the end of your post and I can't delete my previous comment.
DELETE
I've made the USB connector, and got the device unlocked. I'm already on the R release, anyone know if it's safe to use this? thanks in advance
zNiiC said:
What can we do with root?
Click to expand...
Click to collapse
My thoughts exactly.
zNiiC said:
What can we do with root?
Click to expand...
Click to collapse
Dougshell said:
My thoughts exactly.
Click to expand...
Click to collapse
What ever you like. roms can be optimized, build.prop edits for battery and speed, themes if you like.......
Lol, I meant thus far.
Dougshell said:
Lol, I meant thus far.
Click to expand...
Click to collapse
That's exactly what he meant. That's what you can do if you have the knowledge. If you're on this site to get others work, then absolutely nothing can be done.
Anyone done this on the R build yet? I don't want to brick my device lol
beats4x said:
That's exactly what he meant. That's what you can do if you have the knowledge. If you're on this site to get others work, then absolutely nothing can be done.
Anyone done this on the R build yet? I don't want to brick my device lol
Click to expand...
Click to collapse
This is just a boot that boots on the device, not flash. It "should" work with out any issues.
I plan to try it out this weekend when I make time to unlock the boot loader and ect.
wingman_214 said:
This is just a boot that boots on the device, not flash. It "should" work with out any issues.
I plan to try it out this weekend when I make time to unlock the boot loader and ect.
Click to expand...
Click to collapse
Haha, yeah, that "should" is what worries me. And I'm outside of my return window now, so it'd be a real shame to lose the device
I did it yesterday on the R build. Everything went fine and got root access
R build rooted
I successful booted the kernel and have root on the newer R build.
I am trying to root my moto360 but it gets stuck on downloading boot.img . Any solutions?
vincenzo697 said:
I am trying to root my moto360 but it gets stuck on downloading boot.img . Any solutions?
Click to expand...
Click to collapse
The boot image linked in the op must be in your adb folder and renamed to "boot.img".
i know i am using the supertool from rootjunky http://www.rootjunky.com/motorola-moto-360-super-tool/#comment-149
Battery should be full and your display should look like this when connected:
http://m.imgur.com/YvjqY0D
Sent from my GT-N7100 using XDA Free mobile app
I'm using RR 5.6.9 by @tank0412 for last one week.
http://forum.xda-developers.com/zenfone-5/development/rom-resurrection-remix-mm-5-6-7-t3357331
So far I didn't face any freezing or random reboot issues. What I did is as below:
1. Flash/downgrade to UL-ASUS_T00F-WW-2.21.40.30-user firmware.
If you know how to flash stock firmware then skip step 2-12 and just flash it by yourself. These steps are for new users.
2. TURN OFF the device. Press and hold Volume Up+Power to enter to fastboot/droidboot. When the ASUS logo shows up, release the power button and keep on pressed the Volume UP button. This will take you to droidboot/fastboot mode.
3. Check whether your PC detects the fastboot...
Code:
fastboot devices
if not, go to device manager and install the fastboot driver(by online). if fails, install from the PC by selecting the android device from the list.
4. Download this image UL-ASUS_T00F-WW-2.21.40.30-user.zip: http://dlcdnet.asus.com/pub/ASUS/Ze...user.zip?_ga=1.61130092.1708615694.1457697474
If you have different SKU, you need to find the right firmware(version-2.21.40.30) here: https://www.asus.com/Phone/ZenFone_5_A500CG/HelpDesk_Download/
5. Extract fastboot.img, boot.img, recovery.img from the zip file and copy to ADB folder to flash. Copy UL-ASUS_T00F-WW-2.21.40.30-user.zip to ADB folder as well.
6. Run the below commands:
Code:
fastboot flash fastboot fastboot.img
fastboot reboot-bootloader
wait for reboot.....
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
7. Then go to recovery by selecting from the menu, you will an android logo with "!" sign. Press power+vol down+vol up sequentially and simultaneously, don't release any of the buttons. You should be in recovery mode.
8. In the recovery, select wipe data/factory reset
9. Select wipe cache partition
10. Select apply update over adb sideload
11. Now check whether your PC detects the ADB over USB. if not, go to your PC's device manager and install the ADB driver online. if fails, install from the PC by selecting the android device from the list.
12. After successful detection, run below command
Code:
adb sideload UL-ASUS_T00F-WW-2.21.40.30-user.zip
13. Download this official tool for Unlock Bootloader: http://dlcdnet.asus.com/pub/ASUS/Ze...rel.zip?_ga=1.117083014.1481752799.1464212721
A501cg users should get the tool here: https://www.asus.com/Phone/ZenFone_5_A501CG/HelpDesk_Download/
14. Extract the downloaded file and copy the .apk file into you SDcard. Install that .apk(if it says untrusted app, then go to settings>security>enable Unknown sources).
15. Run the installed app and press unlock. wait and let it reboot. After this, your Asus splash screen will become white & bright.
16. Now do a clean flash for any custom rom.
You guys can try it. :highfive:
Note: Few users are having "No Camera" issue for unlocked bootloader. This method will not fix that. Sorry about it, I'm a victim as well.
a8962383 said:
I'm using RR 5.6.9 by @tank0412 for last one week.
http://forum.xda-developers.com/zenfone-5/development/rom-resurrection-remix-mm-5-6-7-t3357331
So far I didn't face any freezing or random reboot issues. What I did is as below:
1. Flash/downgrade to UL-ASUS_T00F-WW-2.21.40.30-user firmware.
If you know how to flash stock firmware then skip step 2-12 and just do it.
2. TURN OFF the device. Press and hold Volume Up+Power to enter to fastboot/droidboot. When the ASUS logo shows up, release the power button and keep on pressed the Volume UP button. This will take you to droidboot/fastboot mode.
3. Check whether your PC detects the fastboot...
Code:
fastboot devices
if not, go to device manager and install the fastboot driver(by online). if fails, install from the PC by selecting the android device from the list.
4. Download this image UL-ASUS_T00F-WW-2.21.40.30-user.zip: http://dlcdnet.asus.com/pub/ASUS/Ze...user.zip?_ga=1.61130092.1708615694.1457697474
If you have different SKU, you need to find the right firmware(version-2.21.40.30) here: https://www.asus.com/Phone/ZenFone_5_A500CG/HelpDesk_Download/
5. Extract fastboot.img, boot.img, recovery.img from the zip file and copy to ADB folder to flash. Copy UL-ASUS_T00F-WW-2.21.40.30-user.zip to ADB folder as well.
6. Run the below commands:
Code:
fastboot flash fastboot fastboot.img
fastboot reboot-bootloader
wait for reboot.....
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
7. Then go to recovery by selecting from the menu, you will an android logo with "!" sign. Press power+vol down+vol up sequentially and simultaneously, don't release any of the buttons. You should be in recovery mode.
8. In the recovery, select wipe data/factory reset
9. Select wipe cache partition
10. Select apply update over adb sideload
11. Now check whether your PC detects the ADB over USB. if not, go to your PC's device manager and install the ADB driver online. if fails, install from the PC by selecting the android device from the list.
12. After successful detection, run below command
Code:
adb sideload UL-ASUS_T00F-WW-2.21.40.30-user.zip
13. Download this official tool for Unlock Bootloader: http://dlcdnet.asus.com/pub/ASUS/Ze...rel.zip?_ga=1.117083014.1481752799.1464212721
14. Extract the downloaded file and copy the .apk file into you SDcard. Install that .apk(if it says untrusted app, then go to settings>security>enable Unknown sources).
15. Run the installed app and press unlock. wait and let it reboot. After this, your Asus splash screen will become white & bright.
16. Now do a clean flash for any custom rom.
You guys can try it. :highfive:
Note: Few users are having "No Camera" issue for unlocked bootloader. This method will not fix that. Sorry about it, I'm a victim as well.
Click to expand...
Click to collapse
When i run unlock application its saying my device its not supported. My device is zenfone 5 a501cg 1.2 ghZ, 2gb ram and 8 gb rom.
Sent from my ASUS_T00J using XDA-Developers mobile app
Well weather this method would work is debatable since I have used various methods posted on ozanks thread but non have worked I even used a debricking method and it still didn't fix freeze this method would only qualify and a downgrade from roms after this
pintuvirani said:
When i run unlock application its saying my device its not supported. My device is zenfone 5 a501cg 1.2 ghZ, 2gb ram and 8 gb rom.
Sent from my ASUS_T00J using XDA-Developers mobile app
Click to expand...
Click to collapse
First of all, please don't quote the whole OP while you are replying.
Yes, it won't work for your device as you have a501cg. You need to get the official unlock tool from this site: https://www.asus.com/Phone/ZenFone_5_A501CG/HelpDesk_Download/
Before that you have to flash or downgrade to *.30.zip firmware.
Sent from my ASUS_T00F using XDA-Developers mobile app
jiyaad1 said:
Well weather this method would work is debatable since I have used various methods posted on ozanks thread but non have worked I even used a debricking method and it still didn't fix freeze this method would only qualify and a downgrade from roms after this
Click to expand...
Click to collapse
Better to give a try. It's been 8 days now and I didn't face the freezing or reboot issue. BTW, which debrick process did u try?
It worked for many: http://forum.xda-developers.com/showthread.php?t=3377455
Sent from my ASUS_T00F using XDA-Developers mobile app
a8962383 said:
Better to give a try. It's been 8 days now and I didn't face the freezing or reboot issue. BTW, which debrick process did u try?
It worked for many: http://forum.xda-developers.com/showthread.php?t=3377455
Click to expand...
Click to collapse
Actually a501 has the SAME unlocker as a500cg. There's only one app that unlocks a wide variety of Asus devices. (Zen6's different afaik).
And we tried to install 2.21.40.30 for base as well and it changed nothing.
And unlocker application doesn't change the working mechanism of phone (we decompiled it).
So, are you sure that you tried to use heavy applications like Youtube or some games?
If you get any user that reports freezes gone; i will try it again with your method.
Thanks for your contribution. Good luck with your method. :laugh:
Btw assuming you have a500cg, that phone can be fixed imo.
ozank said:
Actually a501 has the SAME unlocker as a500cg. There's only one app that unlocks a wide variety of Asus devices. (Zen6's different afaik).
And we tried to install 2.21.40.30 for base as well and it changed nothing.
And unlocker application doesn't change the working mechanism of phone (we decompiled it).
So, are you sure that you tried to use heavy applications like Youtube or some games?
If you get any user that reports freezes gone; i will try it again with your method.
Thanks for your contribution. Good luck with your method.[emoji23]Btw assuming you have a500cg, that phone can be fixed imo.
Click to expand...
Click to collapse
Bro, I'm a heavy user. Many of us had faced forced close for 8 ball pool game. I had it too but after this method no forced close happened again. I'm not sure whether a500cg and a501cg have same app for unlocking. It's a bit confusing to me as they have different sites to download their firmwares and tools. But I'm sure, what ever the phone is a500cg or a501cg, the tool will work if the user has *.30.zip firmware installed.
Sent from my ASUS_T00F using XDA-Developers mobile app
a8962383 said:
Bro, I'm a heavy user. Many of us had faced forced close for 8 ball pool game. I had it too but after this method no forced close happened again. I'm not sure whether a500cg and a501cg have same app for unlocking. It's a bit confusing to me as they have different sites to download their firmwares and tools. But I'm sure, what ever the phone is a500cg or a501cg, the tool will work if the user has *.30.zip firmware installed.
Click to expand...
Click to collapse
Yes because the tool seeks for if.bin on firmware folder and it copies to the sysfs. (You're doing same thing on fastboot when flash ifwi if.bin)
So that's why I don't believe the unlocker tool fixes something.
Anyway, thanks; I will wait for another users that solved the issues with your method and then take a look with my phone.
a8962383 said:
Better to give a try. It's been 8 days now and I didn't face the freezing or reboot issue. BTW, which debrick process did u try?
It worked for many: http://forum.xda-developers.com/showthread.php?t=3377455
Sent from my ASUS_T00F using XDA-Developers mobile app
Click to expand...
Click to collapse
I've tried it. Within the first few minutes, it froze again.
Anyways, thanks for trying.
cnswico said:
I've tried it. Within the first few minutes, it froze again.
Anyways, thanks for trying.
Click to expand...
Click to collapse
Did you downgrade to UL-ASUS_T00F-WW-2.21.40.30-user.zip?
a8962383 said:
Did you downgrade to UL-ASUS_T00F-WW-2.21.40.30-user.zip?
Click to expand...
Click to collapse
Exactly as stated in the instructions. I'll try it a second time.
cnswico said:
Exactly as stated in the instructions. I'll try it a second time.
Click to expand...
Click to collapse
This unlock app its work on first kikat rom 2.19 build. But thing is my device not detecting sim on jelly bean and first kitkat build. I tried many time but not detecting sim. Only start detecting sim from 2.19.40.9 to lollipop rom only.
Sent from my ASUS_T00J using XDA-Developers mobile app
It froze again about 3 hours after I had unlocked with asus tool & flashed RR 5.6.9. And I hate that white & bright splash screen anyways, thanks so much for doing research. I believe we will find out a way to solve this problem some day.
a8962383 said:
Better to give a try. It's been 8 days now and I didn't face the freezing or reboot issue. BTW, which debrick process did u try?
It worked for many: http://forum.xda-developers.com/showthread.php?t=3377455
Sent from my ASUS_T00F using XDA-Developers mobile app
Click to expand...
Click to collapse
I used a method suggested by @dgadelha and it still didn't help and right now I lost my phone to a freak accident so I'm with out a unit for testing ?
tranxuanthang said:
It froze again about 3 hours after I had unlocked with asus tool & flashed RR 5.6.9. And I hate that white & bright splash screen anyways, thanks so much for doing research. I believe we will find out a way to solve this problem some day.
Click to expand...
Click to collapse
Extract splash.bin from rom:
fastboot flash splash splash.bin
or
fastboot flash splashscreen splash.bin
I don't remember which was doing this, but try these
a8962383 said:
Many of us had faced forced close for 8 ball pool game.
Click to expand...
Click to collapse
this is not due to bootloader
I have no problems with bootloader
8 ball force closed on all custom MM rom's
I have no problems except "freeze on 8 ball"
all custom MM rom's used dgadelha's device tree
I think there is a mistake in this
milano88 said:
this is not due to bootloader
I have no problems with bootloader
8 ball force closed on all custom MM rom's
I have no problems except "freeze on 8 ball"
all custom MM rom's used dgadelha's device tree
I think there is a mistake in this
Click to expand...
Click to collapse
You are right. Most of the cross platform developed apps are crashing. It seems like something is wrong with the JavaScript's render engine. I don't play with ROMs. Hope ppl will come forward to have a fix. But to my utter surprise it's been 10days, I still don't have any freezing.
Sent from my ASUS_T00F using XDA-Developers mobile app
Before, following your method with 2.21.40.30-user.zip was not success, but downgrade to 2.22.40.540-user.zip is ok. Unlocked with black logo, white ground but can not flash TWRP, how can install cooked ROM?
My phone is Asus Zenfone 5 T00j A501CG WW. It has 1.6 GHz CPU, 16 gb internal, 2 gb ram. Can this method work if I get the stock firmware you mentioned?
Hi I am new to Android, I follow the steps as mentioned. But not able to after step 7(Press power+vol down+vol up sequentially and simultaneously, don't release any of the buttons. You should be in recovery mode.), I am not go to recovery mode. The phone goes power off mode and is not starting again. Any help is appreciated.
Regards,
Debasish
If you guys, like me , are stucked in an unrooted N1 without Google play services i'll post you this guide on How to port Nokia N1 from A5CNB19 to A5FMB19 without a rooted device.
First of all download the A5FMB19 recovery.img.zip
Then download the A5FMB19_Update.zip
Both Downloadable here ----> https://mega.nz/#F!HSg0FSgI!ZDx1THNk3RlijBTyw71OGg
Important! BOOTLOADER MUST BE UNLOCKED!
Unlock bootloader:
1) Go to your Developer Options and switch on OEM Unlock (4th in list)
2) Plug your N1 to your computer
3) Open your Minimal ADB and Fastboot as administrator and type
Code:
adb reboot fastboot
3a) Otherwise press and hold Power + Vol down
4) Once you're in fastboot mode type
Code:
fastboot oem unlock
on your device, press Vol Up and then accept with Power button
Now your bootloader is unlocked and you can flash the new recovery!
Flashing a new recovery:
1) While in Fastboot mode flash the recovery image with the following command :
Code:
fastboot flash boot recovery.img
WARNING! DO NOT LOCK YOUR BOOTLOADER AGAIN OR THE DEVICE WILL FACTORY RESET BY ITSELF!
2) Now you can Normal Boot your N1 .
3) A Black screen with 2 advice will appear .
-Start by pressing power button
-Factory reset by pressing Volume Buttons.
4)PRESS POWER BUTTON
5)The green droid will display and now you can enter in recovery pressing Power button + Vol Up (DO NOT HOLD THEM)
6)go to " Apply update from ADB" with Vol buttons then enter pressing Power button
7) Upload stock FMB19 update with the following command:
Code:
adb sideload A5FMB19_update.zip
Wait for it to install.
.
.
.
.
8) Lock your bootloader by
Code:
fastboot oem lock
when in fastboot mode
9) Enjoy your Google played Nokia N1
p.s. 1st boot up will take a while
I would like to express my most greetings to jemyzhang who made up the guide on "How to root A5CNB19 & A5FMB19"
If you have any kind of problem please contact me or write below this post so everyone can have a line-guide to follow in case of diseases
Edit : 09/09/2018 Download Links Updated
TheDuke94 said:
If you guys, like me , are stucked in an unrooted N1 without Google play services i'll post you this guide on How to port Nokia N1 from A5CNB19 to A5FMB19 without a rooted device.
First of all download the A5FMB19 recovery.img
Then download the A5FMB19_update.zip
Important! BOOTLOADER MUST BE UNLOCKED!
Unlock bootloader:
1) Go to your Developer Options and switch on OEM Unlock (4th in list)
2) Plug your N1 to your computer
3) Open your Minimal ADB and Fastboot as administrator and type
Code:
adb reboot fastboot
3a) Otherwise press and hold Power + Vol down
4) Once you're in fastboot mode type
Code:
fastboot oem unlock
on your device, press Vol Up and then accept with Power button
Now your bootloader is unlocked and you can flash the new recovery!
Flashing a new recovery:
1) While in Fastboot mode flash the recovery image with the following command :
Code:
fastboot flash boot recovery.img
WARNING! DO NOT LOCK YOUR BOOTLOADER AGAIN OR THE DEVICE WILL FACTORY RESET BY ITSELF!
2) Now you can Normal Boot your N1 .
3) A Black screen with 2 advice will appear .
-Start by pressing power button
-Factory reset by pressing Volume Buttons.
4)PRESS POWER BUTTON
5)The green droid will display and now you can enter in recovery pressing Power button + Vol Up (DO NOT HOLD THEM)
6)go to " Apply update from ADB" with Vol buttons then enter pressing Power button
7) Upload stock FMB19 update with the following command:
Code:
adb sideload A5FMB19_update.zip
Wait for it to install.
.
.
.
.
8) Lock your bootloader by
Code:
fastboot oem lock
when in fastboot mode
9) Enjoy your Google played Nokia N1
p.s. 1st boot up will take a while
I would like to express my most greetings to jemyzhang who made up the guide on "How to root A5CNB19 & A5FMB19"
If you have any kind of problem please contact me or write below this post so everyone can have a line-guide to follow in case of diseases
Click to expand...
Click to collapse
Will this procedure work on a A5CNB19 5.1.1 that has no root and locked bootloader? What are the chances for it to get bricked? Thanks in advance
PS: there are a couple of techies in tailand that say they are able to install CHPlay trough Teamviewer
http://giaiphapandroid.blogspot.pt/2017/06/
The A5FMB19_update.zip download server is now offline. Does anyone have the zip still?
Strangereal said:
The A5FMB19_update.zip download server is now offline. Does anyone have the zip still?
Click to expand...
Click to collapse
I think I should have it. I'll check this afternoon and I will try to upload it somewhere. Thank you :good:
Sent from my Asus ZenFone 2 Laser (ZE500KL) using XDA Labs
Will this procedure work on a A5CNB19 5.1.1 that has no root and locked bootloader? What are the chances for it to get bricked? Thanks in advance
PS: there are a couple of techies in tailand that say they are able to install CHPlay trough Teamviewer
Click to expand...
Click to collapse
You shouldn't try Teamviewer with this kind of "techies" . They can do something bad with your PC or your device as well, I don't trust this kind of things.
Anyways i was stuck in a A5CNB19 without root acces and google play services. To "unlock" my N1 I downgraded it first at the 5.0.1 (I don't remember the firmware code) and then i flashed the Taiwan version (A5FMB19) which actually has Google Play Services installed. Anyways i'm coming with bad news. Unfortunatly I don't have the files you need to downgrade and then to upgrade, anymore. You should try to check out here on XDA if someone has these kind o files. I'll check somewhere if I'm able to download them again and upload them on google drive or something different. Hope I helped you
TheDuke94 said:
You shouldn't try Teamviewer with this kind of "techies" . They can do something bad with your PC or your device as well, I don't trust this kind of things.
Anyways i was stuck in a A5CNB19 without root acces and google play services. To "unlock" my N1 I downgraded it first at the 5.0.1 (I don't remember the firmware code) and then i flashed the Taiwan version (A5FMB19) which actually has Google Play Services installed. Anyways i'm coming with bad news. Unfortunatly I don't have the files you need to downgrade and then to upgrade, anymore. You should try to check out here on XDA if someone has these kind o files. I'll check somewhere if I'm able to download them again and upload them on google drive or something different. Hope I helped you
Click to expand...
Click to collapse
How did you downgrade back to 5.0.1? I'm in the same situation actually (currently on 5.1.1 A5CNB19). My N1 is mostly in good condition but it's completely dead in terms of software support so I thought maybe I could bring it back to life with Google Play store.
Strangereal said:
How did you downgrade back to 5.0.1? I'm in the same situation actually (currently on 5.1.1 A5CNB19). My N1 is mostly in good condition but it's completely dead in terms of software support so I thought maybe I could bring it back to life with Google Play store.
Click to expand...
Click to collapse
I flashed the original recovery of 5.0.1 by Fastboot flash recovery recovery.img and afterward adb sideload update.zip of the old recovery. Unfortunatly i don't have the files anymore so i'm not able to help you . Anyways these are the footsteps to bring back an old version
Sent from my Nokia N1 using XDA Labs
Ok thanks for helpign anyways
TheDuke94 said:
I think I should have it. I'll check this afternoon and I will try to upload it somewhere. Thank you :good:
Sent from my Asus ZenFone 2 Laser (ZE500KL) using XDA Labs
Click to expand...
Click to collapse
Q:
I found it is still unavailiable. Could you please tell how to get this images A5FMB19? thank you in advance.
wang990099 said:
Q:
I found it is still unavailiable. Could you please tell how to get this images A5FMB19? thank you in advance.
Click to expand...
Click to collapse
I was trying to obtain the image but i'm not able to find it anymore. This weekend i'm going to make an OS image with firmware and update. I'm sorry to keep you waiting
Sent from my Nokia N1 using XDA Labs
TheDuke94 said:
I was trying to obtain the image but i'm not able to find it anymore. This weekend i'm going to make an OS image with firmware and update. I'm sorry to keep you waiting
Sent from my Nokia N1 using XDA Labs
Click to expand...
Click to collapse
Any news about that image you're trying to create? Thanks
Got a bad news people, there's no way to find an image file and also, since my N1 is not rooted anymore, i'm not able to find a way to get the image. If someone of you gots a A5FMB19 I , and also the other users will be very gratefull. I apologize for the disguise
See my thread here for the ROM files.
And thanks @TheDuke94 for the helpful how-to!
online.id said:
See my thread here for the ROM files.
And thanks @TheDuke94 for the helpful how-to!
Click to expand...
Click to collapse
Wow! I don't know where you found this rom, but I'm now downloading to have a backup change and I'm going to upload it on Mega to keep this little secret online.
You rock dude
Sent from my Nokia N1 using XDA Labs
TheDuke94's methos worked well for my N1. Just saved it from being 'bricked'.
Really wanna thank you.
It's now 5.1.1. No longer update available. But still fine for me.
siemens_wolf said:
TheDuke94's methos worked well for my N1. Just saved it from being 'bricked'.
Really wanna thank you.
It's now 5.1.1. No longer update available. But still fine for me.
Click to expand...
Click to collapse
Glad it worked! I had the same issue when tried to flash magisk xD anyways still not able to do that, but I'll try to install a lineage OS or something lime that. Unfortunatly, N1 is a Foxconn device so nowadays Nokia (HMD Global) doesn't have anything to bring back to life this device (which still has great hardware specs). BUT I hope a ROM will come for N1 , cause it is a Stock Android device
Sent from my Nokia N1 using XDA Labs
TheDuke94 said:
Glad it worked! I had the same issue when tried to flash magisk xD anyways still not able to do that, but I'll try to install a lineage OS or something lime that. Unfortunatly, N1 is a Foxconn device so nowadays Nokia (HMD Global) doesn't have anything to bring back to life this device (which still has great hardware specs). BUT I hope a ROM will come for N1 , cause it is a Stock Android device
Sent from my Nokia N1 using XDA Labs
Click to expand...
Click to collapse
Just tell us how to flash LineageOS when you secceed. LineageOS was a much better choice for older devices. I just flashed 14.1 for my N7, and it revived. With normal usage, around 5 hrs. SOT, thanks to LineageOS. As I checked, there has been no such Lineage file for Nokia.N1, which was X86-base chip.
Nokia/Foxconn no longer supports N1 device. And it was so pity! N1 is much better off when comparing specs with Nexus.N7. I can get also 5 hrs. SOT with N1 on average usage, but with much brighter screen. And it's faster than N7. So, LineageOS would be a great choice for N1.
All the best wishes to you, TheDuke94. And hope the LineageOS for N1 will come, not long in the future.
Ok people, got strange news.
First , using this method -----> https://forum.xda-developers.com/nokia-n1/development/iovyroot-nokia-n1a5cnb19-a5fmb19-t3466897 I was unable to set root. Then , i rebooted my device, tried again and the result was this :
Now , I downloaded Root Checker in the playstore and it says I don't have Root Permission I think the thing will be much easier using Magisk Manager
Not a geek, really can't help much…but hope everything's good with you, @TheDuke94.
Any Good news, since Apple just released new iPhones?