Related
I see they are flashing custom files / ROMs on the Kindle Fire using fastboot. I believe we are limited on this due to our current bootloader state, but does anyone with experience with Fastboot know if this may be a possible working option until we can get CWM / recovery ?
I agree, can someone please try this? I've seen romified asking this question several times but no one seems to have tried it. The chances aren't great, but it's definitely worth a try.
might be as simple as "adb reboot fastboot"
and then "fastboot oem unlock" or other commands (I'm not too familiar with them myself)
This harks back to the (not so long ago) days of flashing via fastboot on my HTC Magic, which have since passed since I move onto a SGS II.
Edit: Oops it wasn't romified who asked this previously. Can't remember who it was. But either way, that's not really important.
I have not asked about fastboot yet as I just though of it and did some quick research. I am comfortable hacking roms and decompiling files and what not, but bootloaders and hacking recovery is new to me (for now anyway) As soon as I get to where I can I will dig into it further but if someone knows it isn't going to happen with this bootloader, no need in wasting time on it. It could open the door for other possibilities as well. I tried to get fastboot to recognize my NT but no luck. It was just a quick try though.
Did you manage to get the NT to get into fastboot mode though? Probably using the adb reboot fastboot or adb reboot download command (unless we find the hard button shortcut to it)?
I don't have the Nook Touch yet, but will probably be getting one to play with soon (the gf has her eyes on one). Either way, the more capability unlocked, the better.
If you can get the device into fastboot, it's a matter of looking carefully at the USB device tree and seeing that you have a fastboot device listed, then digging through the strings until you find a string you can use to communicate with the device.
If Fastboot isn't included with the NT, it is available with a number of other software packages.
I know it's part of one of the Lenovo LeTools packages, for instance, which is available for download for Windows hosts. If you get the copy from LeTools, be aware that it will install (or try to) the LeTools.apk that's bundled with it from your computer to any bloody Android device that's attached, not just to Lenovo devices. So you may want to delete LeTools.apk after installing and before connecting your NT.
Or you might want to try leaving it there as an experiment. The apk does some interesting things, one of which is make your device discoverable via wifi, at least if it's a Lenovo branded device.
The release of LeTools I just confirmed fastboot for is available at http://consumersupport.lenovo.com/us/en/DriversDownloads/drivers_show_5004.html release IN12STW151WW5.exe.
You don't need to install everything to get fastboot - you can unzip the installer a couple of times to get to the install.msi file for just the tools.
Hi
I've looked around the XDA Forums, and on various other forums. I have a Hipstreet Titan, I tried to root using the Tasselhof's Root package, and it went reasonably well until I selected the option (#3) to copy over the build.prop file. After that I get the Android logo every boot-up. Factory wipe I guess wiped - I don't really have any way to verify. I pushed a different build.prop on, but that didn't seem to take (or make any difference). For some reason my adb shell (whateverother parms) doesn't work. It returns "- exec '/system/bin/sh' failed: No such file or directory (2) -". So I figure the OS has been toasted. (I didn't have this much trouble rooting my LG Eclypse. )
Now, I just need to find an original ROM, or some other slightly modded (rooted would be nice) ROM to get on to my device before I find out how far out my back door I can throw this thing. As this Hipstreet tablet is an off brand (really far off, but hey, I got it free), I haven't been able to find a ROM posted anywhere. Likely I just haven't looked in the right spot yet. Yes, I know, I should have backed up first - but I didn't. As soon as I get an OS working on this, I'll back it up - promise.
I've also tried "adb sideload system.img" using a system image file that comes with the Android ADT kit and the factory recovery mode. That appears to upload the file, reboot the device then report (on the windows terminal) "* failed to write data 'protocol fault (no status)' *". The device reboots into the recovery system screen.
So, if someone would be so kind as to point me to a rom file that will work on this device, it would be most appreciated.
PS this is the Titan rev A, when I got the device (second hand) the Google Play store functioned just fine. The person I got it from is not a techy, so I doubt they applied any root or update to it, so I'm guessing it came already set up.
Ok, let me rephrase simply.
Can someone with a working Hipstreet Titan, rooted or not, please send me, or post a link to their ROM?
Click to expand...
Click to collapse
I know people have this device, and it's quite reasonable to assume that not all of them are bricked, therefore this request is technically feasible. Further, with a number of people posting about this device in technical forums, I know people with technical knowledge own this device.
I would really hate to throw out an otherwise perfectly good tablet.
Jarod997 said:
I would really hate to throw out an otherwise perfectly good tablet.
Click to expand...
Click to collapse
Hi - did you ever resolve this issue?
beach9000 said:
Hi - did you ever resolve this issue?
Click to expand...
Click to collapse
Not yet. I had given up for a while. Most of my internet searches kept coming back to the same few articles on this website.
I have a lead on someone who has another Titan, but they live seven hours away - it's been difficult coordinating a meeting.
Jarod997 said:
Hi
I've looked around the XDA Forums, and on various other forums. I have a Hipstreet Titan, I tried to root using the Tasselhof's Root package, and it went reasonably well until I selected the option (#3) to copy over the build.prop file. After that I get the Android logo every boot-up. Factory wipe I guess wiped - I don't really have any way to verify. I pushed a different build.prop on, but that didn't seem to take (or make any difference). For some reason my adb shell (whateverother parms) doesn't work. It returns "- exec '/system/bin/sh' failed: No such file or directory (2) -". So I figure the OS has been toasted. (I didn't have this much trouble rooting my LG Eclypse. )
Now, I just need to find an original ROM, or some other slightly modded (rooted would be nice) ROM to get on to my device before I find out how far out my back door I can throw this thing. As this Hipstreet tablet is an off brand (really far off, but hey, I got it free), I haven't been able to find a ROM posted anywhere. Likely I just haven't looked in the right spot yet. Yes, I know, I should have backed up first - but I didn't. As soon as I get an OS working on this, I'll back it up - promise.
I've also tried "adb sideload system.img" using a system image file that comes with the Android ADT kit and the factory recovery mode. That appears to upload the file, reboot the device then report (on the windows terminal) "* failed to write data 'protocol fault (no status)' *". The device reboots into the recovery system screen.
So, if someone would be so kind as to point me to a rom file that will work on this device, it would be most appreciated.
PS this is the Titan rev A, when I got the device (second hand) the Google Play store functioned just fine. The person I got it from is not a techy, so I doubt they applied any root or update to it, so I'm guessing it came already set up.
Click to expand...
Click to collapse
It looks like they made a few different versions of the tablet and it matters also about how much storage as to which firmware you should try. The person here: http://www.androidtablets.net/forum...eet-titan-a13-7-inch-tab-firmware-needed.html was able to load the firmware from another device that was similar. There were some major issues, but better to get it running first and sort that out later I guess. But his link has a bunch of other a13 tablet firmwares. If that is the same as yours, possibly one of them will be enough to boot up.
es0tericcha0s said:
It looks like they made a few different versions of the tablet and it matters also about how much storage as to which firmware you should try. The person here: (link manually removed) was able to load the firmware from another device that was similar. There were some major issues, but better to get it running first and sort that out later I guess. But his link has a bunch of other a13 tablet firmwares. If that is the same as yours, possibly one of them will be enough to boot up.
Click to expand...
Click to collapse
Thanks for the help! I'll have a look at some of those. I'd really like to have a tablet back that doesn't have a 3.5" screen.
So I managed to get LiveSuit 1.11 installed on Win 8-64, yes it IS doable. But, my problem is I can't get the tablet recognized. The Power+Vol boot takes it in to "recovery" mode, (so reports "adb devices") - does this keep it from being able to be used by LiveSuit?
"adb wait-for-device" hangs
In my Device Manager I have Android Device->Android ADB Interface, and Universal Serial Bus controllers->USB Device(VID_1f3a_PID_efe8) with a yellow exclamation.
I know I had "adb wait-for-device" passing fine at one point, but I don't remember what I had to do to get there. So much trouble for a free tablet.
I have a Titan that I unfortunately tried to root using what would only work on the ICS model and it's the JB model. It bootloops on the Android boot sequence. I can adb into the tablet and browse it, and I can see in the logcat where it gives up and restarts.
I saw the post on that other forum about using the Tragidy firmware but that file at Dorkfiles now appears to be paywalled. If anyone has that or another compatible firmware already downloaded and would be able to share, that would be wonderful.
At this point the Titan in front of me may as well be a mini cutting board or a large coaster. Not that it matters much, as some store gave it out to my parents for free and we all own better devices. It's just that they don't own any Androids and I thought I could configure this one as an easy remote for them to push content from their media server to their Smart TV instead of using the TV's complicated interface.
cmstlist said:
I have a Titan that I unfortunately tried to root using what would only work on the ICS model and it's the JB model. It bootloops on the Android boot sequence. I can adb into the tablet and browse it, and I can see in the logcat where it gives up and restarts.
I saw the post on that other forum about using the Tragidy firmware but that file at Dorkfiles now appears to be paywalled. If anyone has that or another compatible firmware already downloaded and would be able to share, that would be wonderful.
At this point the Titan in front of me may as well be a mini cutting board or a large coaster. Not that it matters much, as some store gave it out to my parents for free and we all own better devices. It's just that they don't own any Androids and I thought I could configure this one as an easy remote for them to push content from their media server to their Smart TV instead of using the TV's complicated interface.
Click to expand...
Click to collapse
So I managed to get a system backup off of my father-in-law's Titan - just have to figure out how to get it on my brick. I'm having great difficulty trying to do a restore while in recovery mode.
What means did you use to back it up?
Sent from my Nexus 5 using Tapatalk
cmstlist said:
What means did you use to back it up?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
adb backup
Jarod997 said:
adb backup
Click to expand...
Click to collapse
The adb backup command doesn't back up the system files. Unless there's some other way to use it that I'm not aware of?
Sent from my Nexus 7 using Tapatalk
cmstlist said:
The adb backup command doesn't back up the system files. Unless there's some other way to use it that I'm not aware of?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Aw crap, really? The cutting board a-la-iPad commercial is sounding like such a good idea at the moment.
On the good tablet I could get in the shell - "adb shell", and then "su", but then what? How do you copy all the files off the system through the USB onto the computer from the shell? For whatever reason (and I dislike ADB for this) I could not do "adb pull /* /destination-folder/*" - it kept saying that it was skipping a lot of files. Or otherwise if I was trying other variations on commands and parameters, adb would just spew its help page - never mind telling me what's wrong with the command I just entered.
Why, oh why, is it so hard to take a copy of a good working OS and put it on to another tablet?
But, make you a deal - help me get a good system image off this working tablet and I'll toss it to ya.
If you can find the right mount points on the partition table got may be able to make a system dump using dd. But restoring it I have no idea since there's no custom recovery available for this tablet.
Sent from my Nexus 7 using Tapatalk
Hello,
First off, I've gone through the forums and I have looked up other posts and despite everything I cannot figure out how to get my nexus 7 tablet to be recognized by the computer (I tried and after two days of searching for answers I decided to make a post). I like to include this information so people don't assume that I post without browsing or haven't tried anything yet.
The thing that I am having troubles with is that I have a nexus 7 tablet that is softbricked, I have already gone through a lot of ways to fix that problem (I found the best solution is this:http://forum.xda-developers.com/showthread.php?t=1809195). However, the issue is is that I cannot get my computer to recognize the nexus tablet to flash it and restore it back to factory settings.
I have installed and updated the device drivers on my computer, but still I have had no such luck. I found that ADB doesn't recognize the device whilst in the Bootloader, but still will not recognize the device in recovery mode. If anyone has any tips, or suggestions that might work PLEASE let me know, at this point I'm getting desperate and any/all help would be greatly appreciated!
Thank you!
NecroGi said:
Hello,
First off, I've gone through the forums and I have looked up other posts and despite everything I cannot figure out how to get my nexus 7 tablet to be recognized by the computer (I tried and after two days of searching for answers I decided to make a post). I like to include this information so people don't assume that I post without browsing or haven't tried anything yet.
The thing that I am having troubles with is that I have a nexus 7 tablet that is softbricked, I have already gone through a lot of ways to fix that problem (I found the best solution is this:http://forum.xda-developers.com/showthread.php?t=1809195). However, the issue is is that I cannot get my computer to recognize the nexus tablet to flash it and restore it back to factory settings.
I have installed and updated the device drivers on my computer, but still I have had no such luck. I found that ADB doesn't recognize the device whilst in the Bootloader, but still will not recognize the device in recovery mode. If anyone has any tips, or suggestions that might work PLEASE let me know, at this point I'm getting desperate and any/all help would be greatly appreciated!
Thank you!
Click to expand...
Click to collapse
adb is not designed to be usable in bootloader mode. You need fastboot for that. If you have the fastboot.exe program in the same folder as your adb stuff, try this:
fastboot devices
If it reads, then all you need to do is fastboot flash the various .img files back to the tablet. There are tool kits that do this for you, but I prefer doing it manually as there are less chances of things messing up and if they do, you're more likely to know at what step which could be useful for further troubleshooting if need be. It is important to download the correct img files due to differences between the generations and wifi / data enabled ones. There is a flash-all script that you can find in the download of the factory images, which might make it easier, but you can just manually flash the separate files as sometimes you don't need to bother with them all (like the bootloader) though if the script works, then it'll be fine and might make it easier if you are not familiar with the commands.
If you don't have fastboot at all, just grab it from here: http://forum.xda-developers.com/showthread.php?t=2317790
Nexus img files: https://developers.google.com/android/nexus/images
Hit me up on Hangouts if you need more direction.
NecroGi said:
Hello,
First off, I've gone through the forums and I have looked up other posts and despite everything I cannot figure out how to get my nexus 7 tablet to be recognized by the computer (I tried and after two days of searching for answers I decided to make a post). I like to include this information so people don't assume that I post without browsing or haven't tried anything yet.
The thing that I am having troubles with is that I have a nexus 7 tablet that is softbricked, I have already gone through a lot of ways to fix that problem (I found the best solution is this:http://forum.xda-developers.com/showthread.php?t=1809195). However, the issue is is that I cannot get my computer to recognize the nexus tablet to flash it and restore it back to factory settings.
I have installed and updated the device drivers on my computer, but still I have had no such luck. I found that ADB doesn't recognize the device whilst in the Bootloader, but still will not recognize the device in recovery mode. If anyone has any tips, or suggestions that might work PLEASE let me know, at this point I'm getting desperate and any/all help would be greatly appreciated!
Thank you!
Click to expand...
Click to collapse
You won't get adb in bootloader mode.
You have to use the fastboot command.
Please tell the OS on your computer.
Use the tool in my signature as an environment.
Download 7zip, and install that.
Then go here and download the proper image for your device.
It would either be "Factory Images "nakasi" for Nexus 7 (Wi-Fi)" or "Factory Images "nakasig" for Nexus 7 (Mobile)".
Grab the 4.4.2 version.
Extract the downloaded file with 7zip into the "Work" folder in the tool form my signature.
Then extract that "nakasig-kot49h-factory-83d93b5f.tar" file with 7zip.
Then go into the folder that came out of that, and extract the "image-nakasig-kot49h.zip" into the Work folder.
And enter the following commands while in bootloader.
Code:
fastboot oem unlock
fastboot erase userdata
fastboot erase system
fastboot erase recovery
fastboot erase cache
cd nakasig-kot49h
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
Make SURE you grab the correct image for your device. Wifi or Mobile.
I also assume that you know the .img files should be in the Work folder before you type thse commands into my tool.
Hey guys, first of all thank you for the speedy replies and steps I should follow.
Right now I'm using OSX but for the tablet I'm using a virtual Win7 machine to try and get this damn tablet to be recognized by the computer. The process is being delayed a little bit because my micro USB cords are being temperamental, meaning that the tablet has no juice, and when I mess with it (using the power + volume buttons to boot to bootloader/recover) the cord comes unplugged. I know automatically you guys are going to pinpoint this as the source of the issue (mainly because I would too), but it works fine if just laid flat and stays connected. It just has zero charge so when it disconnects/reconnects I literally have to power it back up, just need to wait for it to have some charge before I tinker with it more.
I will post updates after it charges.
Although I already thanked you guys, thanks again for speedy reply. It's much appreciated.
NecroGi said:
Hey guys, first of all thank you for the speedy replies and steps I should follow.
Right now I'm using OSX but for the tablet I'm using a virtual Win7 machine to try and get this damn tablet to be recognized by the computer. The process is being delayed a little bit because my micro USB cords are being temperamental, meaning that the tablet has no juice, and when I mess with it (using the power + volume buttons to boot to bootloader/recover) the cord comes unplugged. I know automatically you guys are going to pinpoint this as the source of the issue (mainly because I would too), but it works fine if just laid flat and stays connected. It just has zero charge so when it disconnects/reconnects I literally have to power it back up, just need to wait for it to have some charge before I tinker with it more.
I will post updates after it charges.
Although I already thanked you guys, thanks again for speedy reply. It's much appreciated.
Click to expand...
Click to collapse
I suggest to STOP!!!
If you are trying to restore the device and the cable disconnects in the middle of it, it might not be recoverable. That would be one of the few ways to really damage the tablet as they are pretty difficult to hard brick. Don't half ass it with stuff like this. A good cable is not THAT much and will certainly be cheaper than a new tablet or getting it to a point where you might have to send it somewhere for service.
I'm not familiar with Macs, but if you are more so, then this might be better than using a Virtual set up:
https://code.google.com/p/adb-fastboot-install/
es0tericcha0s said:
I suggest to STOP!!!
If you are trying to restore the device and the cable disconnects in the middle of it, it might not be recoverable. That would be one of the few ways to really damage the tablet as they are pretty difficult to hard brick. Don't half ass it with stuff like this. A good cable is not THAT much and will certainly be cheaper than a new tablet or getting it to a point where you might have to send it somewhere for service.
I'm not familiar with Macs, but if you are more so, then this might be better than using a Virtual set up:
Click to expand...
Click to collapse
It's actually working fine now (in the sense that the computer can now read it). The Virtual Machine also works just as good, but for some reason the toolkit I'm using won't properly return the tablet to the stock image using the SkipSoft Android ToolKit, so I'm going to have to try and find another way.
Thanks for your guys' help.
Hi all,
Came by a Blackview BV6600 from someone who gave up on it - shipped saying that the device was 'corrupt and couldn't be trusted'. Went back and forth with their crappy customer service and gave up, sold it to me for cheap. It seems like a decently rugged phone but it does have a lot of bloatware and according to some threads on here about the mfgr I don't know if I trust them too much.
I'd like to wipe this phone, and I'm finding it difficult to locate a generic 'How to' for flashing a new OS to a phone. Disclosure; this is the first time I've done something like this. My experience is with computers, I know phones are a different beast and the user has much less freedom due to specifics of the hardware. If I say anything based on incorrect assumptions please correct me.
Again, what I would like to do is akin to installing Linux on what was a Windows box. I'd like to ****can as much weird chinese bloatware as possible (upto and including the entire OS) and replace it with some basic clean open source software. It seems like LineageOS does not have a version for Blackview phones, nor does it have a generic image. I notice that the Android open source project has 'Generic System Images' https://source.android.com/setup/build/gsi#flashing-gsis which sounds like what I want but references a vbmeta.img file which itself, as far as I can tell searching the forums, is likely manufacturer dependent, maybe phone dependent.
Anyway, I'm taking all the steps I see across enough sites to suggest they are platform-independent and won't brick my phone. Been following this video
since it's relatively recent and addresses my specific manufacturer.
So far I have:
Got developer permissions (go to Settings-About Phone, click build number repetitively)
in Settings-System turned on OEM unlocking and USB debugging
Figured out how to put this phone model in fastboot mode (hold volume up during restart)
Installed ADB and Fastboot (Linux), pinged the phone with "adb devices" and checked it's partitioning with " 'adb shell' <enter> 'getprop ro.build.ab_update' " no output, so that suggests 'A only'.
Next step seems to be:
oem unlock using fastboot. I seem to be having trouble here. In fastboot mode connected via USB, I can't detect the device. "Waiting for any device". 'adb devices' gives no response. No idea why. Phone screen looks exactly like in the video, hooked to USB that did return output for USB devices in normal boot mode.
Once I get over this dumb hump, I think I'll need to find a version of TWRP that will work on my device, install TWRP.
At this point I'm even more at sea: Most places suggest Magisk, but I've also seen explainers to wipe the old OS and install LineageOS.
If anyone has advice on what to do from here, specifically the near-term issue of not being able to find my phone via USB debugging while in fastboot mode, please let me know. But of course, long term I'm gonna need to know how to shovel this **** the phone came with out of storage and replace with a clean install so that is welcome as well.
bump
Hisense just released a new device called the A9. Since this phone has Snapdragon 662 I was wondering how easy it would be to root this device. I know there is an EDL for this CPU. The Hisense A5 series was also rootable. Not sure what method was used.
The Onyx Boox Note Air 2 (a 10.3" tablet), which I have, also runs on the same Snapdragon 662 and can be rooted via Magisk. I used the EDL to dump the boot.img on the Note Air 2 to root it via Magisk.
Disclaimer: I'm not a developer or super technical guy, but have rooted a few devices by following guides.
Does anyone know how easy or fast a root would be available? I'm assuming they didn't lock the bootloader on this device as most Chinese devices.
Hello, could you share with us how to root boox device please?
It would be great if GAPPS could be used.
Replying to bump this thread. I have the Hisense A9 and would love to be able to root. It has an option to unlock the bootloader in the developer options if that is helpful.
formeriphoneuser said:
Does anyone know how easy or fast a root would be available? I'm assuming they didn't lock the bootloader on this device as most Chinese devices.
Click to expand...
Click to collapse
Hello and good morning, @formeriphoneuser
I hope you'll always find and get the support you require.
However, prior to your next posting please read the guidances that are stuck on top of every forum like
[Read Before Posting]QUESTIONS DO NOT BELONG IN GENERAL
Hello Everybody, In order to attempt to keep this forum neat and tidy the moderation team is asking you to post your questions into the Questions and Answers (Q&A) forum and not into the General section. You can find the Q&A forum by clicking...
forum.xda-developers.com
and the others. I've moved the thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
I recently good a Hisense A9, and I've been trying to extract the boot.img and / or recovery.img from it (since I can't find either of those online yet). So far I've been trying to get boot.img from EDL mode using this EDL tool. I can boot into EDL mode fine, but when I try to run an EDL command there are lots of errors. It's possible I'm using the wrong Firehose file, but I think it's right. (I'll post a link to the logs below). I've been following this guide mainly. Is anyone else working on this?
*Edit* the firehose file I'm using is 0014d0e100000000_d40eee56f3194665_FHPRG.bin.
Anyway, OP - hopefully I, or someone, can get the boot image or recovery image soon, then we should be able to patch it with Magisk fairly easily and install Google Services etc.
A word of warning to anyone who wants to try working on this - every time I restart after being in EDL mode, the phone goes into a boot loop of sorts. I enter the 6-digit pin at boot-up, and the phone says something in Chinese (which Google translates as something like "optimising the system, please wait", from memory), and then keeps showing the desktop screen for a second, then looping back to the pin code input, then showing the message, and then repeat. If you hold down volume down, it'll go into safe mode, but then the same thing happens when you restart. I've always managed to get out of it, but I'm not 100% sure how! Something like holding the power key down for about 10 seconds while it's looping... The phone vibrates, but doesn't turn off, and then the loop stops and you can enter your 6-digit pin again and it's back to normal. If that doesn't work, then try turning the phone off, then back on again, but holding the power key down so it keeps restarting without fully booting. Last time I made it restart ~5 times, and then it was back to normal. Maybe it cleared some kind of system cache...?
These are the errors I get from the EDL tool when I try to extract the boot image.
https://pastebin.com/ejXfCJs9
https://pastebin.com/5CqUPB0a
https://pastebin.com/LMmEmm6v
RunnyYolk said:
I recently good a Hisense A9, and I've been trying to extract the boot.img and / or recovery.img from it (since I can't find either of those online yet). So far I've been trying to get boot.img from EDL mode using this EDL tool. I can boot into EDL mode fine, but when I try to run an EDL command there are lots of errors. It's possible I'm using the wrong Firehose file, but I think it's right. (I'll post a link to the logs below). I've been following this guide mainly. Is anyone else working on this?
Anyway, OP - hopefully I, or someone, can get the boot image or recovery image soon, then we should be able to patch it with Magisk fairly easily and install Google Services etc.
A word of warning to anyone who wants to try working on this - every time I restart after being in EDL mode, the phone goes into a boot loop of sorts. I enter the 6-digit pin at boot-up, and the phone says something in Chinese (which Google translates as something like "optimising the system, please wait", from memory), and then keeps showing the desktop screen for a second, then looping back to the pin code input, then showing the message, and then repeat. If you hold down volume down, it'll go into safe mode, but then the same thing happens when you restart. I've always managed to get out of it, but I'm not 100% sure how! Something like holding the power key down for about 10 seconds while it's looping... The phone vibrates, but doesn't turn off, and then the loop stops and you can enter your 6-digit pin again and it's back to normal. If that doesn't work, then try turning the phone off, then back on again, but holding the power key down so it keeps restarting without fully booting. Last time I made it restart ~5 times, and then it was back to normal. Maybe it cleared some kind of system cache...?
These are the errors I get from the EDL tool when I try to extract the boot image.
https://pastebin.com/ejXfCJs9
https://pastebin.com/5CqUPB0a
https://pastebin.com/LMmEmm6v
Click to expand...
Click to collapse
Maybe try this loader. This is for sure the one I used for my NA2. Otherwise, you have quite some errors that relate to python. Not sure what the issue is there.
formeriphoneuser said:
Maybe try this loader. This is for sure the one I used for my NA2. Otherwise, you have quite some errors that relate to python. Not sure what the issue is there.
Click to expand...
Click to collapse
Awesome, thanks! I should have mentioned which loader I was using (different to the one you linked). I'll edit my post to say what I used before.
I tried the loader that @formeriphoneuser suggested, but with a similar result. (https://pastebin.com/ucMkEkeW). I also tried with the flag --memory="ufs" in case the device has UFS memory, but similar result.
But the good new is, I've just discovered a reliable way to avoid the boot loop after leaving EDL mode. So to leave EDL mode, make sure any running commands have ended, unplug the device from the computer, and press and hold the eink button (on the left of the phone), volume-up, and power button. Keep them all pressed until the first vibration (after about 15 seconds or so, then release the power button only). Keep the other two pressed while the phone boots, and even while you're entering your 6 digit pin code. When you see the main screen you can release the buttons and your phone shouldn't enter the boot loop. I have no idea how much of that is necessary, but something in there works for me.
I've added an Issue to the github repo for the EDL tool I'm using. Other than that, I think I've hit a brick wall and won't be able to do any more for now. Unless anyone knows how to check that the firehose file is correct for my device, and update it if it's not. Hopefully Hisense will release the stock firmware, or send us an OTA update or something.
Does this work? if the Bootloader could be unlocked.
Arthurliao said:
Does this work? if the Bootloader could be unlocked.
Click to expand...
Click to collapse
The problem with a GSI is that Android doesn't have partial refresh support for the eInk display, which means a driver has to be written from scratch, otherwise the display will be verrrrrry slow.
RunnyYolk said:
I tried the loader that @formeriphoneuser suggested, but with a similar result. (https://pastebin.com/ucMkEkeW). I also tried with the flag --memory="ufs" in case the device has UFS memory, but similar result.
But the good new is, I've just discovered a reliable way to avoid the boot loop after leaving EDL mode. So to leave EDL mode, make sure any running commands have ended, unplug the device from the computer, and press and hold the eink button (on the left of the phone), volume-up, and power button. Keep them all pressed until the first vibration (after about 15 seconds or so, then release the power button only). Keep the other two pressed while the phone boots, and even while you're entering your 6 digit pin code. When you see the main screen you can release the buttons and your phone shouldn't enter the boot loop. I have no idea how much of that is necessary, but something in there works for me.
I've added an Issue to the github repo for the EDL tool I'm using. Other than that, I think I've hit a brick wall and won't be able to do any more for now. Unless anyone knows how to check that the firehose file is correct for my device, and update it if it's not. Hopefully Hisense will release the stock firmware, or send us an OTA update or something.
Click to expand...
Click to collapse
Bit of a long shot here, but I vaguely remember having trouble with EDL on my Oneplus 6T and I think the solution was to use a USB2 port instead of USB3.
RunnyYolk said:
I tried the loader that @formeriphoneuser suggested, but with a similar result. (https://pastebin.com/ucMkEkeW). I also tried with the flag --memory="ufs" in case the device has UFS memory, but similar result.
But the good new is, I've just discovered a reliable way to avoid the boot loop after leaving EDL mode. So to leave EDL mode, make sure any running commands have ended, unplug the device from the computer, and press and hold the eink button (on the left of the phone), volume-up, and power button. Keep them all pressed until the first vibration (after about 15 seconds or so, then release the power button only). Keep the other two pressed while the phone boots, and even while you're entering your 6 digit pin code. When you see the main screen you can release the buttons and your phone shouldn't enter the boot loop. I have no idea how much of that is necessary, but something in there works for me.
I've added an Issue to the github repo for the EDL tool I'm using. Other than that, I think I've hit a brick wall and won't be able to do any more for now. Unless anyone knows how to check that the firehose file is correct for my device, and update it if it's not. Hopefully Hisense will release the stock firmware, or send us an OTA update or something.
Click to expand...
Click to collapse
Also, looking at your pastebins, It seems you are running Ubuntu via a Parallels Virtual Machine. I would suggest using the LiveDVD from the EDL github repo and running it on bare metal to rule out any system related issues. Given that the pastebins show errors relating to libusb1.py, there is a good chance your issues are due to the emulated USB controller provided by Parallels.
matteqa said:
Also, looking at your pastebins, It seems you are running Ubuntu via a Parallels Virtual Machine. I would suggest using the LiveDVD from the EDL github repo and running it on bare metal to rule out any system related issues. Given that the pastebins show errors relating to libusb1.py, there is a good chance your issues are due to the emulated USB controller provided by Parallels.
Click to expand...
Click to collapse
I tried booting the liveDVD from the repo in Parallels, but it wouldn't boot, saying something like Ubuntu was missing. But I'll try it as a bootable USD drive. I won't be able to do it until next weekend at the earliest, but I'll report back when I've tried that method. Thanks for your suggestions!
So I bought a USB drive and flashed the liveDVD from the repo to it, but my only computers are Macs and will recognise the USB drive as bootable - I've tried Fat32 / HFS+ file systems, made sure it's a GUID partition table, and used both Etcher GUI and terminal's `dd` to burn the image to the drive, but still the USB never shows up in the startup utility. Anyway, I've hit a roadblock on this for now - I think my next options are to either pick up a cheap Windows laptop, or put a bounty out for boot.img (or preferably full root! )
RunnyYolk said:
So I bought a USB drive and flashed the liveDVD from the repo to it, but my only computers are Macs and will recognise the USB drive as bootable - I've tried Fat32 / HFS+ file systems, made sure it's a GUID partition table, and used both Etcher GUI and terminal's `dd` to burn the image to the drive, but still the USB never shows up in the startup utility. Anyway, I've hit a roadblock on this for now - I think my next options are to either pick up a cheap Windows laptop, or put a bounty out for boot.img (or preferably full root! )
Click to expand...
Click to collapse
Just checking, have you tried the macOS version of the EDL tool? All of your pastebins are from ubuntu parallels, however there is also a native macOS version in the github repo.
matteqa said:
Just checking, have you tried the macOS version of the EDL tool? All of your pastebins are from ubuntu parallels, however there is also a native macOS version in the github repo.
Click to expand...
Click to collapse
Ah, that's a good call! I did try the native Mac version on one machine, but it wasn't able to find libusb library, so I started using parallels / ubuntu, and then basically forgot that the native mac version existed! So thanks for the reminder - I tried it yesterday on an older Mac, and the native EDL client seems to be working properly. Unfortunately I think the firehose / loader files I have aren't correct. When I ran it with a loader I get sahara - [LIB]: Unexpected error on uploading, maybe signature of loader wasn't accepted ?
type object 'req' has no attribute 'image_id', and then I tried running it without any loader and got sahara - [LIB]: Couldn't find a loader for given hwid and pkhash (0014d0e100430000_56d3f3c74a52172b_[FHPRG/ENPRG].bin) :(.
So I guess we need the correct loader for the A9. I'm pretty clueless about how these files come to exist in the first place (do they have to come from the manufacturer, or can we build them ourselves?), but anyway I'll open a new issue on Github and see if the developer of the client can help.
For completeness' sake, here are logs from each attempt at reading boot_a (I tried three different loaders, each one with and without --skipresponse, and then once with no loader).
https://pastebin.com/AA9d5Tdh
https://pastebin.com/gXHS9pYN
https://pastebin.com/6e5FeWDc
https://pastebin.com/8dGWFNau
https://pastebin.com/iTd8ZsVH
https://pastebin.com/2esPvxyX
https://pastebin.com/Pvz9YxfE
https://pastebin.com/D47mPKt6
*edit* This is the issue on Github: https://github.com/bkerler/edl/issues/303
RunnyYolk said:
Ah, that's a good call! I did try the native Mac version on one machine, but it wasn't able to find libusb library, so I started using parallels / ubuntu, and then basically forgot that the native mac version existed! So thanks for the reminder - I tried it yesterday on an older Mac, and the native EDL client seems to be working properly. Unfortunately I think the firehose / loader files I have aren't correct. When I ran it with a loader I get sahara - [LIB]: Unexpected error on uploading, maybe signature of loader wasn't accepted ?
type object 'req' has no attribute 'image_id', and then I tried running it without any loader and got sahara - [LIB]: Couldn't find a loader for given hwid and pkhash (0014d0e100430000_56d3f3c74a52172b_[FHPRG/ENPRG].bin) :(.
So I guess we need the correct loader for the A9. I'm pretty clueless about how these files come to exist in the first place (do they have to come from the manufacturer, or can we build them ourselves?), but anyway I'll open a new issue on Github and see if the developer of the client can help.
For completeness' sake, here are logs from each attempt at reading boot_a (I tried three different loaders, each one with and without --skipresponse, and then once with no loader).
https://pastebin.com/AA9d5Tdh
https://pastebin.com/gXHS9pYN
https://pastebin.com/6e5FeWDc
https://pastebin.com/8dGWFNau
https://pastebin.com/iTd8ZsVH
https://pastebin.com/2esPvxyX
https://pastebin.com/Pvz9YxfE
https://pastebin.com/D47mPKt6
*edit* This is the issue on Github: https://github.com/bkerler/edl/issues/303
Click to expand...
Click to collapse
Have you tried to read from "boot" instead of "boot_a". Maybe hisense isn't using A/B partitions since they don't care about google play certification. Also, have you tried using --memory=ufs.
Otherwise, it may be that the loader has a custom signature. As far as I know, the loader is proprietary and you have to get it from the manufacturer.
@RunnyYolk
I've also just found a patched version of a SDM662 loader on another forum that might work.
I've reuploaded it here: https://cloud.matteqa.com/index.php/s/M6MxgPFDsYwaKP6
matteqa said:
@RunnyYolk
I've also just found a patched version of a SDM662 loader on another forum that might work.
I've reuploaded it here: https://cloud.matteqa.com/index.php/s/M6MxgPFDsYwaKP6
Click to expand...
Click to collapse
Thanks! I tried this loader, and also the --memory=ufs flag / "boot" alternatives as you suggested, but had the same errors as before. I'm pretty sure I saw boot_a and boot_b directories somewhere when I was exploring the filesystem in adb shell, but I'll double check again when I have time.
Are there any other avenues I could try to root this device? I wonder if there's any point trying to boot TWRP from an A7? Am I right in thinking I can `fastboot boot recover.img` without risk of bricking the phone? (Ie just booting rather than flashing.)... Maybe I'm clutching at straws...