Bootloop after 6.0.1 OTA update - Nexus 9 Q&A, Help & Troubleshooting

2 weeks ago I did a 6.0.0 to 6.0.1 OTA update and my device went into I a so called bootloop.
I tried everything on http://www.skipsoft.net/?page_id=1647 - without success.
The factory reset and the options in the recovery menu of the Nexus 9 did not help.
I cannot load a new image because I did not Enable the developer options nor the USB debugging via the menu when the device was OK.
I installed the SKIPSOFT UNIFIED ANDROID TOOLKIT and connected to my Nexus 9 (WiFi).
I connected successfully to the device and tried the UNLOCK BOOTLOADER part of the app.
It didn't work - it gives "ERROR - you have to enable debugging mode in order to unlock".
So, the question is: Can you unlock the bootloader with the SKIPSOFT UNIFIED ANDROID TOOLKIT if one did not Enable the enable developer options nor the usb debugging via the android menu?
If not, can you suggest to me what may be my options as I am stuck. Warranty of the device has just passed.
Thank you in advance,
S.

If you can get into recovery, you might be able to sideload the OTA again: - http://forum.xda-developers.com/nexus-9/help/failed-marshmallow-update-stock-android-t3226704
Get the January OTA zip from here: - http://forum.xda-developers.com/showpost.php?p=64693937&postcount=557
Or whatever OTA you need from that thread.

xyz

Thank you very much for your comment corkiejp. I just followed the sideloading sith the January 6.0.1 update packae and.... IT WORKED Thank you very much. God bless this community

bluesharp said:
Thank you very much for your comment corkiejp. I just followed the sideloading sith the January 6.0.1 update packae and.... IT WORKED Thank you very much. God bless this community
Click to expand...
Click to collapse
Your welcome, remember to enable "OEM unlocking" in developer options, even if you have no intentions of using it at present!

corkiejp said:
Your welcome, remember to enable "OEM unlocking" in developer options, even if you have no intentions of using it at present!
Click to expand...
Click to collapse
I just enabled oem unlock. i am writing this from my nexus 9, and i have you friend to thank for

I had same problem, couldn't get the recovery method to work properly.
Was able to return to HTC for repair, just received it back today.... got even worse. Started to set up again.
Here is list of problems:
first it froze on the homescreen on initial start up
froze while updating the google apps
now doing the reboot thing
frozen on the lock screen
can hear a soft 'tap' sound while in locked mode
Needless to say will be returning to retail for full refund.
Something tells me either Android or manufactures haven't fully tested Marshmallow properly with hardware, as having bad problems with my LG G4 also on M6 and gone for repair.

...
So I have the same problem. While updating to 6.0.1 there was an error message and after that it got into a bootloop. Can I sideload when I don't see character identifier for my device as described in point 4 in the link? All I see is "OS - n/a"

Kuhuma said:
So I have the same problem. While updating to 6.0.1 there was an error message and after that it got into a bootloop. Can I sideload when I don't see character identifier for my device as described in point 4 in the link? All I see is "OS - n/a"
Click to expand...
Click to collapse
At your own risk. You could try with the latest OTA zip linked above.
It shouldn't do anymore damage, probably just fail if your system was on an earlier version than what this updates from.
If it fails, try an earlier OTA.
Report back on your progress.

corkiejp said:
At your own risk. You could try with the latest OTA zip linked above.
It shouldn't do anymore damage, probably just fail if your system was on an earlier version than what this updates from.
If it fails, try an earlier OTA.
Report back on your progress.
Click to expand...
Click to collapse
I followed every step but I'm stuck at step 9 and 10. Neither I see "Wipe Cache" nor "Apply update from ADB". Is it because I never unlocked developer options on my device? I'm in Fastboot Mode btw.

Kuhuma said:
I followed every step but I'm stuck at step 9 and 10. Neither I see "Wipe Cache" nor "Apply update from ADB". Is it because I never unlocked developer options on my device? I'm in Fastboot Mode btw.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Very strange that your recovery screen does not have them options. (dev. options shouldn't matter).
Try rebooting in recovery and check them again.
You can also do a factory reset from the hboot menu, which might resolve your problems.

corkiejp said:
Very strange that your recovery screen does not have them options. (dev. options shouldn't matter).
Try rebooting in recovery and check them again.
.
Click to expand...
Click to collapse
Ah, this helped me. I have to press volume up only once. :silly:
I'll report my progress.
---------- Post added 29th January 2016 at 12:25 AM ---------- Previous post was 28th January 2016 at 11:28 PM ----------
It worked. Thank you so much for your help. Only thing i f***** up, was the recovery mode. I held the volume up button for too long and always ended up in fastboot mode.

Related

Root

NEW: CF-Auto-Root flashable: http://download.chainfire.eu/595/CF-Root/CF-Auto-Root/CF-Auto-Root-flounder-volantis-nexus9.zip
Will update this post soon-ish!
--- old post follows ---
This took a few hours more than I had hoped, because it's both the first firmware on a new Android version as well as 64-bit. While there have been 64-bit builds of the SuperSU binary for a while now, they were untested until now, and unsurprisingly there were a few (minor) issues to fix before it worked properly.
As such, this root includes SuperSU v2.18, which is a special build for the Nexus 9, which you should definitely not try to put on any other device, nor should you put an older version of SuperSU on the Nexus 9.
I have not yet updated the CF-Auto-Root framework to be able to patch the kernels live (needed on 5.0) or support 64-bit, so this is a more manual root than usual.
It pretty much comes down do:
- enable oem unlocking in Android's developer options
- fastboot oem unlock
- fastboot boot inject.img
- fastboot flash boot patched.img
The included README.TXT is a little bit more extensive, but not by much, and if you don't know what the above does then maybe you shouldn't bother (yet).
Please note that many root apps will have issues with both Android 5.0 as well as 64-bit. There may also be more issues with SuperSU on 64-bit that I have not found yet.
Guess it's time to fix up CFAR and update the new How-To SU with all the 5.0 specifics. That'll all take some time, though.
Click to expand...
Click to collapse
^^^ from my G+
Download:
http://download.chainfire.eu/592/CF-Root1/Nexus9-root-SuperSU-v2.18.zip
Knew it wouldn't take long! Thanks!
This came faster than my tablet
Awesome. Just got mine today and already unlocked, just waiting on word from you to root. Can't wait!
Sent from my Nexus 9
can’t wait
need root so bad
Boom
Rooted ?
nexus 9 rooted ty so much
A quick video guide for those of you that prefer visual aids.
Now we need busybox
Can't get it to work...
Booted both images just as instructed. Then first full boot after booting the images, it won't accept touch at the encryption screen. Hold the power button then it reboots and boots fine. Open SuperSU app and it says no root binary... I'm still fidgeting with it.
leviwhite9 said:
Booted both images just as instructed. Then first full boot after booting the images, it won't accept touch at the encryption screen. Hold the power button then it reboots and boots fine. Open SuperSU app and it says no root binary... I'm still fidgeting with it.
Click to expand...
Click to collapse
had the same issue. went back to the stock boot.img, disabled security and set to swipe, reflashed inject.img & patched.img. worked good, turned security back on but didnt choose to enforce on start up. guessing might be an issue with that..? havent tried with that re-enabled.
Oh yea!! Trying it right now!
eurominican said:
Oh yea!! Trying it right now!
Click to expand...
Click to collapse
Working good
Already edodexed the ROM
renzyyy said:
had the same issue. went back to the stock boot.img, disabled security and set to swipe, reflashed inject.img & patched.img. worked good, turned security back on but didnt choose to enforce on start up. guessing might be an issue with that..? havent tried with that re-enabled.
Click to expand...
Click to collapse
That was the issue! Turned off security and rebooted the two images and I had SU access. Turned pattern lock with boot enforcement and it broke SU. It is the boot time security that breaks this.
leviwhite9 said:
That was the issue! Turned off security and rebooted the two images and I had SU access. Turned pattern lock with boot enforcement and it broke SU. It is the boot time security that breaks this.
Click to expand...
Click to collapse
Also, for anyone that missed this or didnt know about it (like me), you have to tick off "Enable OEM unlock"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nice work! Seems to work well so far - now as others stated I just need busybox - seems Titanium Backup is not detecting root and needs it? Or TB could be incompatible.
Sean09 said:
Nice work! Seems to work well so far - now as others stated I just need busybox - seems Titanium Backup is not detecting root and needs it? Or TB could be incompatible.
Click to expand...
Click to collapse
Get the test build of TB
I have it and its working well
USBhost said:
Get the test build of TB
I have it and its working well
Click to expand...
Click to collapse
Thanks very much, got test 6 from their twitter and it works!
Is there a recovery yet??

[HOW] [Mi 3] [CM 13] [ERROR: 7] How to update CyanogenMod weekly updates

My device Mi3 is running on CyanogenMod 13 and latest TWRP recovery. Unable to install weekly updates of CyanogenMod. Recently, got an update cm-13.0-20160516-NIGHTLY when i tried to install that there is an dialog box of "Apply Update" You are about to update bla bla bla... Note: This feature requires a compatible Recovery or updates will need to be installed manually. I didn't get what it means and i thought TWRP is a valid recovery so proceeded from that. After few minutes it rebooted the device top recovery and nothing happened from that. So i rebooted the system again searched over Internet about the issue haven't found any perfect solution (within what i found) but i tried by copying the update file to /sdcard (i mean root directory) and tried to install the update manually by using TWRP recovery but it is showing an error "Updater process ended with ERROR: 7 Error installing zip file '/sdcard/cm-13.0-20160516-NIGHTLY-cancro.zip' Updating partition details......done"
Can you help me out how to install the update and also tell me what I've done wrong so that i will not do that again.
Thanks in advance.
Dude, the answer to your question is in the first post of CM13 FAQ.
Go in here and follow the guide.
https://jrizzoli.github.io/dotfiles/
Hi @diongdyh
sorry for late reply, please help me with a step that is mentioned in the link you've given.
"Run flash_all.bat (on windows) or flash_all.sh (on OS x and Linux - it's suggested to open it from a terminal in these systems)"
Does it mean to run in cmd or what. Please help me out. If you can please elaborate that step.
manideeproyal said:
Hi @diongdyh
sorry for late reply, please help me with a step that is mentioned in the link you've given.
"Run flash_all.bat (on windows) or flash_all.sh (on OS x and Linux - it's suggested to open it from a terminal in these systems)"
Does it mean to run in cmd or what. Please help me out. If you can please elaborate that step.
Click to expand...
Click to collapse
Just connect your device and double click on "flash_all.bat"(I'm assuming you to be on Windows) and it'll do the rest
Well I encountered the same problem a while ago.. I just flashed miui 8 through twrp.. and booted and again flashed latest cm13 and it worked.. No problems so far..
Sent from my MI 3W using XDA-Developers mobile app
@ssasin.monish said:
Just connect your device and double click on "flash_all.bat"(I'm assuming you to be on Windows) and it'll do the rest
Click to expand...
Click to collapse
ok i'll do the same. I doubt whether the device needs to be in fastboot mode or normal system. If you can clear this i'll proceed because previously i tried the same but in fastboot and the device is recognized i checked by 'fastboot devices'.
manideeproyal said:
ok i'll do the same. I doubt whether the device needs to be in fastboot mode or normal system. If you can clear this i'll proceed because previously i tried the same but in fastboot and the device is recognized i checked by 'fastboot devices'.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It is literally written in the second step. Bootloader=Fastboot mode.
diongdyh said:
It is literally written in the second step. Bootloader=Fastboot mode.
Click to expand...
Click to collapse
i've done the same @diongdyh, after selecting run something went in a flash on the desktop screen and nothing happened on my device and its still in fastboot mode. i think booting to miui 8 and then installing cm13 will be a better option as suggested by @sidhg for me as i'm not getting exactly what to do
even I am having the same problem, I nothing happpens on clicking on flash all file.........
manideeproyal said:
i've done the same @diongdyh, after selecting run something went in a flash on the desktop screen and nothing happened on my device and its still in fastboot mode. i think booting to miui 8 and then installing cm13 will be a better option as suggested by @sidhg for me as i'm not getting exactly what to do
Click to expand...
Click to collapse
Yes it'd be best that you flash miui 8 with fastboot/bootloader
http://bigota.d.miui.com/6.6.1/cancro_alpha_images_6.6.1_20160516.0000.22_6.0_cn_2231b4fcb7.tgz

How to update LG Leon H340N to Android M and Unlock the Bootloader

How to update LG Leon H340N to Android M and Unlock the Bootloader
1. The first thing that you need to do is to download the following zip-archive, it contains all the tools that you need + the actual firmware file:
https://mega.nz/#!QgwDHYpB!7TCpc0_ycqjMimhFkHe3yq172tfu__8XIXRJxoxOYHQ
2. After downloading and extracting the archive, run the file named "LG-Mobile-Driver_v4.0.4.0.exe" as administrator, follow the instructions on the screen.
3. Turn off your phone and then hold the volume up button while plugging in the USB-cable to your computer, the phone should enter download mode.
4. Navigate to the folder named LG Flash Tool 2014, open the file named "LGFlashTool2014.exe". When the software is open, change the type to "3GQCT", the phone mode to "Emergency" and then select the .KDZ-file named "H340n20A_00_0512.kdz", then click the button "Normal Flash".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5. A popup will now appear with the title "Read Phone Information", press the button "Start".
6. A new window should now be visible with the title "Select Country & Language", press the button "Clear phone Software update Registry". In the box country, select "Different Country", then in the box language select your language. Then press OK.
7. The firmware should now be flashed over onto your phone, it may take a few minutes and the phone will automatically reboot when it's done.
How to unlock the bootloader after flashing the firmware:
Open "Settings" and then go to "About Phone", then click on "Software info", then tap on the entry "Build info" a few times till developer mode is enabled. Then go back and enter "Developer options", then active "Enable OEM unlock"
First question:
Don't we have to do something after enabling OEM unlock? I mean, I think it's just enable the unlocking itself. After that we can do it via fastboot commands (fastboot oem unlock). Am I right?
Second question:
LG's site says that unlocking is irreversible. But there is a command to do that: fastboot oem lock. Or it isn't working on LG devices?
Can you use this .kdz file on any LG Leon H340n phone? I my current is V10g. That wouldn't be a problem?
xHair said:
Can you use this .kdz file on any LG Leon H340n phone? I my current is V10g. That wouldn't be a problem?
Click to expand...
Click to collapse
I've flashed it on my nordic LG Leon without issues, but I cannot guarantee that this will work for everone.
Sent from my SM-G928F using Tapatalk
I'm gonna test it on both my h345 and ms345.
all work perfect! with a lg leon h340n italian version (tim). THANKS
I am getting this message every time I reboot what is that and what must I do to not see this
My LG Leon is H340N (TIM Version) Italy
Nickblorck said:
I am getting this message every time I reboot what is that and what must I do to not see this
My LG Leon is H340N (TIM Version) Italy
Click to expand...
Click to collapse
I'm having the same issue as well, but it's nothing to worry about and isn't that annoying either way.
Sent from my SM-G928F using Tapatalk
GethPrime said:
I'm having the same issue as well, but it's nothing to worry about and isn't that annoying either way.
Sent from my SM-G928F using Tapatalk
Click to expand...
Click to collapse
IOk then I hope when the original version of my phone comes I won;t have this prob
ninjasinabag said:
I'm gonna test it on both my h345 and ms345.
Click to expand...
Click to collapse
Did it work for you? Im debating on whether or not to try it
ricbaez said:
Did it work for you? Im debating on whether or not to try it
Click to expand...
Click to collapse
you cant installa that kdz on H345 and ms345 get hardbrick, dont try guys!!!
This rom work perfect on all European H340n!
there's just a boring initial message. Jump it.
Trying this out on my 345, will post results ASAP,
Edit: Phone bricked, I do not suggest doing this on the T-Mobile Leon phone, I also am responsible of everything that happened to the phone, and thanks, nonetheless.
this will work on h340ar?
ricbaez said:
Did it work for you? Im debating on whether or not to try it
Click to expand...
Click to collapse
On my ms345 it did, but I lose my radio in the process. No signal.
My h345 went utter apesh*t and I'm afraid to try again.
I can confirm, this works on H340AR.
Q
Is there any way to flash TWRP recovery in 6.0 without rooting after enabling OEM Unlock?
Worked on EE UK H340n running 5.0.1 -- does not offer option to use SD as internal storage but I am going to try a factory reset and see if this changes
---------- Post added at 04:26 PM ---------- Previous post was at 04:02 PM ----------
Still the same, after factory reset it only offers the option of portable storage, not format as internal... why is doing this?
Ok - factory reset doesn't work, but there is a way, needed to use adb, have to use this method from a post about a samsung phone here: I am unable to post ext links, search for bgr galaxy-s7-edge-tips-microsd-adoptable
install adb,
sm list-disks to list the disks
sm partition disk:179,64 private
where 179,64 is the name of my disk from the results of the sm-list disks command
now it works as internal storage for data and apps
martinsgo said:
I can confirm, this works on H340AR.
Click to expand...
Click to collapse
Witch version did you use? Has the oem unlock for the bootloader?
Thanks.

[ROOT] [TWRP] Sm-j7108 j7108 twrp 3.1.1

TWRP 3.1.1-0 is out now for all currently supported devices.
What's new in 3.1.1-0:
Backups will now include adopted storage keys (Dees_Troy)
Fixed an adb restore issue (bigbiff)
Fixed rebooting when no OS is present (Dees_Troy)
Fixed line wrapping in the GUI terminal (_that)
Donate for me is very much appreciated.
To close Frp Lock, enable Developer Options(google it for step), enable OEM Unlock before flashing
If your device don't have twrp, download, extract one time and flash with odin:
https://mega.nz/#!qR0X3bjY!q-_zzXlPA0tGM4i-3LNN5f88Birrkiifhg5eu2kM0HA
If you have twrp already, download this, put in your phone or sd card, then flash using twrp.
install using twrp HOME+POWER+ volume up: https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
what a twrp look like:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks! All works without problems.
4z5ku said:
Thanks! All works without problems.
Click to expand...
Click to collapse
thanks. press the "Thanks" for both comment and the thread.
You might want to check AxvY rom
Locked SM-J7108. Didn't worked.
Hello,
I've tried to unlock my SM-J7108 with this method (ant it's not the first one that I tried) but after run i run Odin it tells me in the phone:
"Installation Failure
You need to unlock your device to install a custom OS"
I've changed the options in the phone to developer mode, enabled USB debugging and unlocked factory protection.
How can I unlock it? I don't have the google apps and I'm desperate to put another rom.
Thank you in advance.
Bruno Rodrigues said:
Hello,
I've tried to unlock my SM-J7108 with this method (ant it's not the first one that I tried) but after run i run Odin it tells me in the phone:
"Installation Failure
You need to unlock your device to install a custom OS"
I've changed the options in the phone to developer mode, enabled USB debugging and unlocked factory protection.
How can I unlock it? I don't have the google apps and I'm desperate to put another rom.
Thank you in advance.
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-j7/development/rom-axvy-rom-sm-j7108-stable-sexy-af-t3687461
mtp not working.
jonathanmohamed said:
mtp not working.
Click to expand...
Click to collapse
No idea how to fix mtp
Hello,
twrp-3.1.1-J7108.7z with insertion J7108ZHU2BRA2 it is not established. At attempt to stitch the previous version J7108ZHS1BQI1 ODIN informs on an error cm.bin FAIL! Whether it is possible to receive ROOT in this situation?
4z5ku said:
Hello,
twrp-3.1.1-J7108.7z with insertion J7108ZHU2BRA2 it is not established. At attempt to stitch the previous version J7108ZHS1BQI1 ODIN informs on an error cm.bin FAIL! Whether it is possible to receive ROOT in this situation?
Click to expand...
Click to collapse
I am not sure what you meant. try to look at the video at here and make a reference: https://forum.xda-developers.com/galaxy-j7/development/rom-axvy-rom-sm-j7108-stable-sexy-af-t3687461
doulc said:
I am not sure what you meant. try to look at the video at here and make a reference: https://forum.xda-developers.com/galaxy-j7/development/rom-axvy-rom-sm-j7108-stable-sexy-af-t3687461
Click to expand...
Click to collapse
Hello,
I have not correctly asked a question. J7108ZHU2BRA2 is an updating of an insertion of the manufacturer (android 6.01). The specified reference interesting. Whether it will be possible to return if necessary on android 6.01?
Hello, I flashed the twrp, Odin said that it succeeded, but when run recovery mode, there's no TWRP, a phone still goes into old, factory recovery mode. Is there any way to fix that?
jonathanmohamed said:
mtp not working.
Click to expand...
Click to collapse
Hello friend. It seems you too facing the same issue I wasted my weekend on. Have tried various tricks but after failing all did windows oS changed. Give it a try but before that you can try these options and if you succeed its worth saving your time.
1. Open device manager- Go to drivers- Uninstall Portable Devices MTP driver- Refresh to re-install.
2. Open device manager- update driver of portable devices
3. Re-Install samsung usb driver manually.
You can find details step in you tube for solutions to mtp device installation failed.
IF NON OF THESE WORK FOR YOU CHANGE THE OS on your pc. AS earlier I was on win7 Ultimate now changed to win7 Professional. Don't know how but it worked for after all day wasted trying all possible solutions.
Hello, I flashed the twrp, Odin said that it succeeded, but when run recovery mode, there's no TWRP, a phone still goes into old, factory recovery mode. Is there any way to fix that?..............version J7108ZHS2BRC1
---------- Post added at 05:02 PM ---------- Previous post was at 05:01 PM ----------
how to unlock bootloader
Can not install on the J7108ZHS2BRC1 software version
hapz said:
Hello, I flashed the twrp, Odin said that it succeeded, but when run recovery mode, there's no TWRP, a phone still goes into old, factory recovery mode. Is there any way to fix that?..............version J7108ZHS2BRC1
---------- Post added at 05:02 PM ---------- Previous post was at 05:01 PM ----------
how to unlock bootloader
Click to expand...
Click to collapse
Dear, You need to install Samsung CROM Service 1.0.8 to unlock device before. https://www.apkmirror.com/apk/samsu...-service-1-0-8-android-apk-download/download/ Good luck
please help me sir, i always failed when installing twrp for Samsung J7 SM-J7108, i already unlocked on OEM and i have enabled usb debug mode.

Unbrick Asus MemoPad FHD 10 LTE (ME302KL)

Hey Guys,
tried to install LineageOS on my mothers tablet, but forgot to unlock bootloader first, so i got a softbricked device like some other guys here.
Because i haven´t found a solution/tutorial here, i tried some things out and now i got a working device
Unbrick The Brick
I found a version in this forum, which installs a ofw -> https://w3bsit3-dns.com/forum/index.php?showtopic=545744&st=2260
My Device was connected in this mode and via cmd : "adb devices" it was listet
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After unzipping 0.rar, i startet a cmd as administrator, navigated with cd to the unziped folder and startet "flashall.cmd"
The Device starts again
Install OFW
Unfortunetly the Unblock Bootloader APK from Asus ended up with an error , i tried a lot with adb install *.apk and so on, but nothing worked out... Therefore i installed the latest OFW
You need an SD-Card and the latest Version (https://www.asus.com/Tablets/ASUS_MeMO_Pad_FHD_10_ME302KL/HelpDesk_Download/)
-> For me it is the "ASUS MEMo Pad FHD 10 LTE Firmware: V10.10.3.39 Only for WW SKU (Android 4.2.2)"
Copy the unzipped zip (you will see what i mean) to the SD-Card and unname it to "APQ8064_SDUPDATE.zip"
Insert the micro SD card into the tablet.
Turn off the tablet.
Press and hold Volume Up + Power Key, wait until the bootloader logo appears, and then the FW update process begins. (if this don´t work out try the APK "Recovery Reboot")
After the completion the device will automatically reboot.
Perform the factory data reset.
IUnlock Bootloader with the official APK
-> https://www.asus.com/de/supportonly/ASUS MeMO Pad FHD 10 LTE/HelpDesk_Download/ -> Utilities -> Expand -> "Unlock Device App"
Install TWRP
-> https://forum.xda-developers.com/android/general/recovery-twrp-3-1-1-0-asus-me302kl-t3609759
Install LineAgeOS
-> https://forum.xda-developers.com/an.../rom-8-0-0-lineageos-15-0-unofficial-t3693838
Enjoy
I had some hope when I saw this thread. I had problems with the bootloader unlock too.
slungshot said:
I had problems with the bootloader unlock too.
Click to expand...
Click to collapse
And it helped?
My advice to anyone trying to revive this old tablet is to just buy a new one, no matter what the cost and you will come out ahead in comparison to time wasted trying to resurrect this old beast. Still if you are like me and perhaps when you arrive here are "already in way too deep", here are some hints to get you going. I'm 2 weeks into playing with this thing but making good progress. Wishing I'd just bought a new one but since I usually forget everything I learned dealing with ROM builds a few weeks after I set it aside,I can't say I learned a valuable lesson so I'm not sure of the benefit.
First of all, to ensure you don't brick this thing, be sure to RESTORE TO FACTORY before unlocking. Then once set to factory defaults and you are configuring it anew again, when you get to the screen asking to sign into Google, then don't do it because if you do, when you run the unlock routine it will go into a loop asking for your Google ID and password. Then when you sideload in the Assus unlock app and also accept any upgrades that Asus provides if at this point you have never logged into Google, the only requirement of this unlock routine is that you have a working wifi accessed so you will never get into the Google ID loop if you don't have a Google sign-in account set up.
So, I've loaded every version, evaluated them and rejected all but 14.1 due to some quirk or another. My mistake was loading multiple zips after the unnlock (including Gapps up front, a no-no in my opinion) and this has left me yet to load any of the Gappas package yet, discovering that is what gave me my black screen initially. I now have a full suite of mapping software loaded and working plus many basic language tools and other apps that support traveling and using this device as a guide. I have side loaded about 25 apps and all is well so far without the play store. I have the GPS working (couldn't get it to work in 13.x and 15.x versions) and additionally I was able to load Magisk systemless, Xposed V25 systemless, XprivacyLUA and a long list of Xposed modules that all work perfectly, plus I have a functional root. I haven't tried any super secure apps like banking because I haven't even set up playstore. So right now I have a great functioning device that is not so Googled-up. I am not sure if I will load the 7.1 Gapps at this point now but I plan to get everything working on this device I can without Google Playstore and the other Google suite and see just how far I can get without Google apps. I do miss the voice typing, however.
Another thing that will get you confused with this tablet is the first time after flashing it with the TWRP recovery and just as you enter fastboot reboot on your computer and press the enter key for the very first time, you have to hold in the power button and up-volume button on the tablet at the same time you reboot with fastboot and if you don't when you reboot after the flash of the new recovery, the stock ROM will revert the TWRP recovery.img back to stock. I know, it sounds hard to believe but if you flash it and don't get the TWRP menu on the next recovery boot, this is what happened.
https://w3bsit3-dns.com/forum/index.php?showtopic=545744&st=2260
link not working

Categories

Resources