Related
I went to flash cyanogenmod 10.1.
backed up rom via clockwork.
wiped data, flashed new rom.
flashed gapps.
I think i flashed the wrong gapps
upon boot I get "setup wizard has stopped" as well as one regarding gapps.
this prevents me from using the rom. I can access the calender and clock that is all. not the settings or reboot menu.
I can access the built in storage via windows, shows up as a nexus 7.
Ok, not a big deal, I will boot into recovery via the bootloader.
That no longer works. Sits at a google screen forever
Ok, I will use fastboot via the bootloader....
That no longer works. As soon as a usb cable touches the nexus either power or pc it freezes the bootloader requires a reboot.
windows rejects the usb and states is malfunctioned and unrecognised (though it works fine in the rom)
fastboot doesn't see the device.
I've tried:
three usb cables.
windows safe mode.
different ports
uninstall/install drivers.
nexus tool kit (doesnt recognise device)
wiggling the cable as suggested
anybody got an idea how I can either get the bootloader not to freeze when using a usb cable or how to boot into some kind of recovery (which was there!!!!!)
please? :fingers-crossed:
Something seems a little off here.
Was it a gapps package for some other device? Hard to see why flashing something to /system would produce the result you got, as the (gapps) edify script would at most specify a mount of "system", not a /dev/block/ device name.
Does adb work (with the ROM booted)? If so, can you get a root shell or install .apks?
The fact that the ROM boots suggests that the bootloader is working correctly enough to load and execute the LNX (boot) image. That means that in principle you could flash (using the "dd" command) a recovery image to the boot partition from a root-privileged command line (either an adb session or a terminal emulator). Performing a regular (power button) restart would boot you into a recovery session.
Obviously, this hinges on you getting a command line somehow with your reduced-functionality ROM limping along as it is. It's not obvious to me how you will make that happen though.
I am not at all confident that this will fix the bootloader <--> USB issue without somehow reflashing the bootloader without using fastboot!. The only way this has been observed for the N7 has been with the OTA process and a stock recovery - the OTA puts an image (**note - important!** this OTA bootloader image is slightly different from the bootloader image in the factory/fastboot ROMs) into the USP partition and some magic occurs on the next boot.
Well, anyway there's some ideas. Would you mind identifying the "wrong" gapps that you used? For the life of me I can't see how it caused the symptoms you are observing...
good luck
Hi. Many thanks.
Ok.....
Gapps. I downloaded the appropriate package via the link on the Rom page. However, I flashed a jellybean package I'd downloaded for my one x. I may be naive in thinking that Gapps is Gapps no?
I deduced it was that having googled the setup wizard problem and seeing that others had had it.
Bootloader.
Again. Ive googled around and can see many have the freezing bootloader with usb issue. Some say its the cable. Some say its the pc. But it does it with the charger as well. Again this is an issue for some. not sure what to do! Works fine until the cable goes in.
Recovery.
Again I know its an issue booting recovery from bootloader. I've read you need the usb in to a pc to make it happen. Obviously that's a no go for me
Adb.
Never really used it. Used fastboot many times. I assumed you need to be able to access the developer options and activate debugging etc within the Rom to allow it to work? I can not do that. Its around 10% funtional. I can place a reminder on the calender but that's about it! No way to system settings.
Sorry if thats teaching you to suck eggs. You obviously know your stuff, just wanted to make it clear.
Ta.
Sent from my HTC One X+ using xda app-developers app
olly2097 said:
Recovery.
Again I know its an issue booting recovery from bootloader. I've read you need the usb in to a pc to make it happen. Obviously that's a no go for me
Click to expand...
Click to collapse
A normally functioning tablet does NOT require you to be plugged in to a PC in order to boot the recovery from the bootloader menu. Maybe you are saying something else here, but I trust you've tried starting the recovery without anything plugged in at all.
Unless you can get the recovery working, the only hope you have is somehow levering up what you have available to gain a privileged thread of execution. Obviously that's going to be pretty challenging.
good luck - you're going to need it.
PS: could you provide a URL to the *wrong* One X gapps download? I think the gapps bundle ships with system libraries - I want to peek at those libs to see if there are any hardcoded block device paths that might explain the queerness you observed. (I can't imagine why this would be the case, but...)
bftb0 said:
A normally functioning tablet does NOT require you to be plugged in to a PC in order to boot the recovery from the bootloader menu. Maybe you are saying something else here, but I trust you've tried starting the recovery without anything plugged in at all.
Unless you can get the recovery working, the only hope you have is somehow levering up what you have available to gain a privileged thread of execution. Obviously that's going to be pretty challenging.
good luck - you're going to need it.
PS: could you provide a URL to the *wrong* One X gapps download? I think the gapps bundle ships with system libraries - I want to peek at those libs to see if there are any hardcoded block device paths that might explain the queerness you observed. (I can't imagine why this would be the case, but...)
Click to expand...
Click to collapse
yeah, tried both ways.
The gapps I downloaded was a while ago. I've deleted it. was for 4.1.1
anyway. I....
Booted to bootloader, selected recovery, pressed power and rammed in the usb cable at the same time.
recovery
now running rom fine after flashing TW recovery via toolkit and mounting to pc.
I cant explain it. it took forever. but thank you
Hello everyone on the XDA community.
This is my first post here ..!
To begin excuse my very bad English, I used a translator to do this. Second, moderators apologies if it is not the right place, I ask a little patience and if you need to edit or move the topic, are in every right to do so.
Thanks in advance.
WARNING: This method has been tested by me, but do not hold me responsible for lost data on their devices or if they suffer irreparable damage. The method should be used with caution, following the steps explained below and must possess knowledge of the use of the tools used. USE AT YOUR OWN RISK.
Tools to be used:
BLU Phone Drivers
Universal ADB Drivers
SP Flash Tools v5.1436.00.000
Studio C D536U V08 5.0 Generic Stock Rom
Kingo Root
Easy Magic TWRP Installer for MediaTek
The first step and most important is: BACKUP, support all device data if possible make a backup of the complete ROM Stock, since in case of a "sudden death" can use this to revive the device. In the XDA Developers forums are methods to do this kind of support.
Steps that I have followed for an update ROM Stock, rooting and subsequent installation of custom recovery:
If you have any drivers installed for your BLU device uninstall them before seeing step 2.
Install the device driver for BLU
ADB drivers installed Universal
Enable USB debugging on development options
Download and install the ROM Stock mentioned above using the following::
Open SP Flash Tool.
Click scatter-loading then select the scatter file inside the ROM you downloaded (must be unzipped of course).
Change "Download" to "Firmware upgrade" (under scatter-loading file).
Click in "Download" button.
Take battery out of your phone and insert it again. make sure your phone does not turn on (If phone has an internal battery then just make sure the phone is off).
Plug in your phone to your PC.
The green check mark means you're good to go.
After installing the new ROM Stock, or if you were already using that version of the ROM Stock must install the Kingo Root, then connect your device and the program will recognize it immediately. The whole process is very simple and takes very little time, stay tuned to the screen of your device for confirmations.
Already having installed and running ROM Stock and rooting and undamaged device, run the program TWRP Setup, this will create the MTK-TWRP folder on your desktop, in it we find the TWRP.exe program which execute and follow the steps described in THIS POST.
And with that we have our rooting device with a new version of ROM Stock and custom recovery.
FINAL NOTE: In my case after installing the new version of ROM Stock did a search for update from the device, and found a new version: BLU_D536U_V10_GENERIC. The downloaded and installed before proceeding with the routing and the installation of custom recovery.
I hope you can use this guide and is very useful for everyone.
Best regards.
New Link Added 16/04/2015https://mega.co.nz/#F!TplRURRI!LyAuAlNIBND_AOgu3bx6tQ
Thanks for the guide, but the rom Studio C D536U V08 5.0 Generic Stock Rom in the mega link, is not available, can you upload?
tttony said:
Thanks for the guide, but the rom Studio C D536U V08 5.0 Generic Stock Rom in the mega link, is not available, can you upload?
Click to expand...
Click to collapse
Hi.
The following directory on the website of Mega contains all the Stock ROM for BLU devices, look inside the folder named "STUDIO SERIES" the "STUDIO 5 C - D536" folder, there you can download the ROM Stock V8 Generic.
https://mega.co.nz/#F!TplRURRI!LyAuAlNIBND_AOgu3bx6tQ
BLU Phone Drivers [link broken]
SP Flash Tools v5.1436.00.000 [link broken]
I have a bricked BLU Studio 5.0 C D536L. Can I flash this rom and files?
I don't know if D536U and D536L are the same devices (maybe L and U only a local id).
I just got this phone from Walmart, even though I didn't use your method to root, as my rom is newer than the rom you provide, mine rom is BLU_D536U_V11_GENERIC seemed pointless to downgrade, I did download your Studio C D536U V08 5.0 Generic Stock Rom as it contained a file I needed to manually root my device.
I use Linux not windows, so the splash tool doesn't help, none the less I was able to root without any problems, using the one file from Studio C D536U V08 5.0 Generic Stock Rom.
Thanks
Vampirefo
Need a pointer or two.
vampirefo said:
I just got this phone from Walmart, even though I didn't use your method to root, as my rom is newer than the rom you provide, mine rom is BLU_D536U_V11_GENERIC seemed pointless to downgrade, I did download your Studio C D536U V08 5.0 Generic Stock Rom as it contained a file I needed to manually root my device.
I use Linux not windows, so the splash tool doesn't help, none the less I was able to root without any problems, using the one file from Studio C D536U V08 5.0 Generic Stock Rom.
Thanks
Vampirefo
Click to expand...
Click to collapse
Hello. I have the same phone and conundrum. Sure would appreciate any pointers you could throw my way about successfully rooting this critter. It's a BLU Studio 5.0 Ce D536 Unlocked Dual SIM 5.0 Phone Android KitKat CellPhone.
There was a sale on ebay selling this new for 68.00 so I bit the bullet and bought it. Sure would appreciate it. I use both Linux and windows so I can relate. Any pointers would be great,Thanks!
rwilcher said:
Hello. I have the same phone and conundrum. Sure would appreciate any pointers you could throw my way about successfully rooting this critter. It's a BLU Studio 5.0 Ce D536 Unlocked Dual SIM 5.0 Phone Android KitKat CellPhone.
There was a sale on ebay selling this new for 68.00 so I bit the bullet and bought it. Sure would appreciate it. I use both Linux and windows so I can relate. Any pointers would be great,Thanks!
Click to expand...
Click to collapse
Your device is different than mine, I don't know anything about your phone.
Sent from my BLU STUDIO 5.0 C using Tapatalk
rwilcher said:
Hello. I have the same phone and conundrum. Sure would appreciate any pointers you could throw my way about successfully rooting this critter. It's a BLU Studio 5.0 Ce D536 Unlocked Dual SIM 5.0 Phone Android KitKat CellPhone.
There was a sale on ebay selling this new for 68.00 so I bit the bullet and bought it. Sure would appreciate it. I use both Linux and windows so I can relate. Any pointers would be great,Thanks!
Click to expand...
Click to collapse
Post 3 seems to have files for your phone, should be able to use those files to root your device.
I had to build a custom recovery for my device, I built Carliv 3.3 recovery and TWRP 2.6.8.0 for my device.
Sent from my BLU STUDIO 5.0 C using Tapatalk
Root BLU Studio 5.0 C success
vampirefo said:
Post 3 seems to have files for your phone, should be able to use those files to root your device.
I had to build a custom recovery for my device, I built Carliv 3.3 recovery and TWRP 2.6.8.0 for my device.
Sent from my BLU STUDIO 5.0 C using Tapatalk
Click to expand...
Click to collapse
Thanks for that. Worked but was scary. Had to change shorts afterwards
Brick/Loop in Recovery.
Hey alakentu, thanks for this great thread. I have a problem at the moment: My, Studio BLU Studio 5.0 C (D536U), boots into the recovery and that is all. If I select Factory Mode it gets stuck on the BLU boot animation. I need to flash a new ROM through the original recovery and I need help with this. Can somebody help me ?
I'll give it a try
I have a 5.0C that has one SIM disabled. The SIM was filled with a platic blank that was glued down. I plan on backing up the custom Digicel ROM (D526 I think) and try to load the D536U stock ROM. I assume that if the hardware isn't customized, the stock ROM will have the code that enables and controls the two SIMS. :fingers-crossed:
I rooted and updated my previously locked phone to the V11 generic ROM. The generic ROM:
1. enabled the SIM that was blocked from the OEM.
2. unlocked both SIM slots.
The upgrade was well worth the trouble that I had with properly loading the USB drivers on my Windows 8 PC.
Same exact quandary here as @blackvitriol. My d536u (Studio 5.0 C) sticks at the Blu splash screen. Is there an RUU mode of sorts with this device? If so, how do I access it without being able to fully boot this device?
Sent from my HTC6535LVW using XDA Free mobile app
jmvaught said:
Same exact quandary here as @blackvitriol. Sticks at the Blu splash screen. Is there an RUU mode of sorts with this device? If so, how do I access it without being able to fully boot this device?
Sent from my HTC6535LVW using XDA Free mobile app
Click to expand...
Click to collapse
SOLVED!! (Not that this is an active thread or anything)
So, in ALL of my research I didn't find one single instruction to fix the bootloop, corrupted ROM issue I had. Many claimed to be able to fix this issue, but all fell short because of ONE SINGLE error in the command line. I know, that's all it takes, BUT it may be difficult to figure out (as it was for me). This is all assuming you have your drivers installed and at the very least Minimal ADB/Fastboot functioning.
1. download the factory image (zip, rar, whatever) and UNPACK it somewhere you can easily find in Windows.
2. place the boot.img and system.img files in the same folder as adb.exe and fastboot.exe
3. put your device in Fastboot by doing the following:
a. press and hold Vol Up AND Power until you see the LCD flicker dark (you'll know it when it happens about 3 seconds into holding. Nothing else will happen yet. Nothing will appear on your LCD.)
b. press Vol Up twice and then Vol Down
*you should see three lines pop up in white text on your screen and it should show Fastboot beneath that. If not, pop that battery out and start over. It may take practice to get it right.
4. open a command window in your adb/fastboot folder.
5. Type the following:
fastboot devices
(your device should show up after you hit enter)<---don't type this
fastboot flash boot boot.img
(you should get some action on your device showing it flashed OK as well as in your command window)<---or this
fastboot flash /system system.img
(you should see it working on your device's LCD counting up from 0% to 100%)<---or this
fastboot reboot
(now wait and watch your device come back to life)<---or this
So what's different here from the other instructions out there? You're flashing the system partition by typing "/system system.img" instead of "system system.img"
Any questions, feel free to ask. Have a good one and good luck.
If I've helped you in any way and you want to help support my kids' college fund, please consider buying me a cup of coffee.
jmvaught said:
Same exact quandary here as @blackvitriol. My d536u (Studio 5.0 C) sticks at the Blu splash screen. Is there an RUU mode of sorts with this device? If so, how do I access it without being able to fully boot this device?
Sent from my HTC6535LVW using XDA Free mobile app
Click to expand...
Click to collapse
i threw away that phone and bought a LG Tribute. Best decision ever. Also, thanks for teaching me this new word: quandary
jmvaught said:
SOLVED!! (Not that this is an active thread or anything)
So, in ALL of my research I didn't find one single instruction to fix the bootloop, corrupted ROM issue I had. Many claimed to be able to fix this issue, but all fell short because of ONE SINGLE error in the command line. I know, that's all it takes, BUT it may be difficult to figure out (as it was for me). This is all assuming you have your drivers installed and at the very least Minimal ADB/Fastboot functioning.
1. download the factory image (zip, rar, whatever) and UNPACK it somewhere you can easily find in Windows.
2. place the boot.img and system.img files in the same folder as adb.exe and fastboot.exe
3. put your device in Fastboot by doing the following:
a. press and hold Vol Up AND Power until you see the LCD flicker dark (you'll know it when it happens about 3 seconds into holding. Nothing else will happen yet. Nothing will appear on your LCD.)
b. press Vol Up twice and then Vol Down
*you should see three lines pop up in white text on your screen and it should show Fastboot beneath that. If not, pop that battery out and start over. It may take practice to get it right.
4. open a command window in your adb/fastboot folder.
5. Type the following:
fastboot devices
(your device should show up after you hit enter)<---don't type this
fastboot flash boot boot.img
(you should get some action on your device showing it flashed OK as well as in your command window)<---or this
fastboot flash /system system.img
(you should see it working on your device's LCD counting up from 0% to 100%)<---or this
fastboot reboot
(now wait and watch your device come back to life)<---or this
So what's different here from the other instructions out there? You're flashing the system partition by typing "/system system.img" instead of "system system.img"
Any questions, feel free to ask. Have a good one and good luck.
If I've helped you in any way and you want to help support my kids' college fund, please consider buying me a cup of coffee.
Click to expand...
Click to collapse
Question/Comment...& Thank you.. However I am attempting to sideload adb style ROM from my BLU 5.5 to another's BLU 5.0 C D536u. Any non USB, PC Solutions? Last night we attempted to back up my system to an SD but failed. Pls I've spent hours researching I've installed the Necessary apps (from what I've read), pls help. Thanks again tho for posting this very useful info
Ivy.Crystal said:
Question/Comment...& Thank you.. However I am attempting to sideload adb style ROM from my BLU 5.5 to another's BLU 5.0 C D536u. Any non USB, PC Solutions? Last night we attempted to back up my system to an SD but failed. Pls I've spent hours researching I've installed the Necessary apps (from what I've read), pls help. Thanks again tho for posting this very useful info
Click to expand...
Click to collapse
Why are you trying to put 5.5 rom on 5.0?
Sent from my Venue 8 3830 using Tapatalk
I'm trying to find the 5.0 stock ROM to download it to my SD so the other person can put it in that way.
Or if u can just help me figure out how to get the 5.0C out of bootloop using my phone? Pls
Sent from my BLU STUDIO 5.5 C using Tapatalk
Anyone install the new update? My phone shows v14 is available, date 9/9/2015.
Sent from my BLU STUDIO 5.0 C using Tapatalk
So im thinking of purchasing one of these when the come out here and i was wondering about an android to windows os hack. Will there be one in the immediate future and will dual booting be an option?
The hardware is exactly the same.
There must be a way to dual boot, hopefully others on this forum can figure out how to do this if Lenovo doesn't facilitate dual boot themselves
Best
I believe there's a different BIOS for Win vs Android. Could have sworn I saw the Windows BIOS posted on the Lenovo support site prior to the Oct 17 launch. It seems gone now though, unless I'm missing something or went to the wrong link? Unlikely you can install Win without a different BIOS.
There is some clear hardware differences with the Android and Windows tablets. Specifically, 2 different physical layouts for the halo keyboard, where the windows one has defined left and right mouse click buttons. There doesn't seem to be any way of accessing the BIOS on the Android tablet, and it does have the usual Android power + volume up, power + volume down recovery options, so it looks like it boot directly to the boot loader.
The Bios is still there ... but how would you flash it?
http://support.lenovo.com/de/de/products/Tablets/Yoga-Series/YOGA-Book/downloads/DS119182
ok so there is also android open source code available in their site, any chance of making a custom rom?
I wonder if we could flash the Chuwi 12 roms onto this given that Chuwi12 has dual boot already?
This is reallly really stupid to me, why not provide dual boot in the first place? I would not mind shelling out $100 more for a dual boot version. Now if I want the windows version I will need to spend another $550 to get another OS with the same device. I will end up having 2 same devices, but that is so anti-mobile really. Do I have to carry 2 hardware devices so i can have 2 OSes at the same time?
Lenovo get some grip please and provide a dual OS version.
win 10 driver
Today, the windos 10 drivers are online..
The drivers you get with levono support with input of the serial number
It must now be possible to build a dual system
Tastertur chipset audio and more .
igelelf said:
Today, the windos 10 drivers are online..
The drivers you get with levono support with input of the serial number
It must now be possible to build a dual system
Tastertur chipset audio and more .
Click to expand...
Click to collapse
Could you post the link for the windows 10 drivers? also any idea on how to unlock the bootloader?
Hi,
earthCallingAngela did unlock the bootlader. .
My background knowledge about booting is very low. But I think there are huge differences between Android and Windows. I think If a system can boot via PC-Bios or Android-Boot-Loader is "on the chip". If this is correct you would need a Android-Boot-Loader that does boot into a windows ... IMO this is no "easy to do". May be the guys who did create Remix OS found a way to do that ...?
Can we use Chuwi 12's disk image somehow? It comes with dual boot.
hajkan said:
Can we use Chuwi 12's disk image somehow? It comes with dual boot.
Click to expand...
Click to collapse
Are the two the same hardware? My understanding is that unless the hardware is very similar, you can't use other ROMs without a *TON* of work.
so i was able to install android x86 6.0 on my yoga book, unfortunately i managed to do it over my windows install so now i just need to reinstall windows lol.....
---------- Post added at 06:35 PM ---------- Previous post was at 05:54 PM ----------
decided to install 7.0 over my 6.0 install i just made and messed everything up. now im back to just trying to get gparted to run so i can reformat and start over.
bisharat said:
Could you post the link for the windows 10 drivers? also any idea on how to unlock the bootloader?
Click to expand...
Click to collapse
http://support.lenovo.com/kr/en/pro... and Software|Drivers and Software&beta=false
you can download yogabook win10(64bit) driver here.
edited--
you should change operating system dropdown menu from android to windows10
Hi & Happy New Year
Now it's possible to get root with android version
I have a YogaBook with Windows version ; Someone can make a backup Android version?
Maybe it's possible to create a dual boot with the windows version I cross the fingers :fingers-crossed:
Where and how?
ThomasHardy said:
Hi & Happy New Year
Now it's possible to get root with android version
Click to expand...
Click to collapse
someone can said me, where i found an android image? (original yoga book, of course) i try to install Remix OS and Android-x86 6.0-r1 released from Android-x86.org but, its can't run. graphics issues and reboot.
i install in a MicroSD and boot it booting yogabook hold volume up + power boton and select boot menu, but it fail on boot.
i have yoga book windows. any idea?
thanks
sorry for my english..
I'm exploring this as well.
Since the BIOS and drivers available (just tested with my serial#), it does seem like it would be relatively easy to dual-boot, provided you can get past the loader issue.
I've done many dual-boot setups, just not since the Win7 days, with the Win8 and forward it's gotten quite a bit trickier, the loader does a bunch of "extra" stuff, boot timing and such, to protect itself.
I've also never done an Android/Windows dual-boot, mostly just Win/Win or Win/Unix.
I think you'd have to figure out how to bootstrap these, so the custom loader can take over, and load from there, but this is a bit beyond my Android capabilities.
Has anyone even tried this? I assume the power/volume keys must work, to get at the loader?
Hi there !
I've just unlocked my Yoga Book's android bootloader and made a backup. I'm trying to install Windows 10 and replace Android with it. The problem is that I don't know how to boot the device from the USB drive.
Does anyone know how to do that ? Even if rooting is required ?
P.S. : I can't google it as all results link to "how to boot a PC from android device", which is the reverse...
Totjoss said:
Hi there !
I've just unlocked my Yoga Book's android bootloader and made a backup. I'm trying to install Windows 10 and replace Android with it. The problem is that I don't know how to boot the device from the USB drive.
Does anyone know how to do that ? Even if rooting is required ?
P.S. : I can't google it as all results link to "how to boot a PC from android device", which is the reverse...
Click to expand...
Click to collapse
simple...you can't do that! it's not possible to boot usb from android bootloader or recovery.
I started this thread: (https://forum.xda-developers.com/axon-7/help/help-loss-root-twrp-t3781054)
a while back and ended up never solving my issue, eventually giving up and living with an unrooted phone.
Anyhow I've been trying again to get to the bottom of the issue and after another day of fruitless research here I am hoping to bring it back to your attention.
Does anyone around here regularly use a mac to perform adb commands? I'd love to get some help trying to get fastboot working again.
Should I just give up and find a Windows computer to do this?
Thanks for reading
alajoy said:
I started this thread: (https://forum.xda-developers.com/axon-7/help/help-loss-root-twrp-t3781054)
a while back and ended up never solving my issue, eventually giving up and living with an unrooted phone.
Anyhow I've been trying again to get to the bottom of the issue and after another day of fruitless research here I am hoping to bring it back to your attention.
Does anyone around here regularly use a mac to perform adb commands? I'd love to get some help trying to get fastboot working again.
Should I just give up and find a Windows computer to do this?
Thanks for reading
Click to expand...
Click to collapse
That guy was horribly wrong and sorry you had to live with an unrooted phone for so long. But in newer versions of Nougat (i think B32 or B35) they removed fastboot and you could not boot into it. I have a way of being able to install TWRP here without fastboot (assuming you're on an Oreo bootstack, otherwise you can do almost everything in that thread except use a TWRP for Nougat instead). I haven't tried this, but if you have stock recovery, try downgrading to Nougat B19 by using an official SD card update and using apply update from SD card in stock recovery. Haven't found an official SD card update for you but I've only done a little bit of searching.
edit: ive only found B19 Nougat full image , but here: https://mega.nz/#F!kYtRAJjJ!5tD1zPpo0nw2tJwhANA9pQ!tNsQhD5Y
download A2017U-7.1.1-B19-Full-326200B1901A2017UV1.1.0B19.zip and extract it and put update.zip in your sd card. boot into stock recovery and use apply update from sd card and select it. hopefully it works and it will downgrade
Teet1 said:
That guy was horribly wrong and sorry you had to live with an unrooted phone for so long. But in newer versions of Nougat (i think B32 or B35) they removed fastboot and you could not boot into it. I have a way of being able to install TWRP here without fastboot (assuming you're on an Oreo bootstack, otherwise you can do almost everything in that thread except use a TWRP for Nougat instead). I haven't tried this, but if you have stock recovery, try downgrading to Nougat B19 by using an official SD card update and using apply update from SD card in stock recovery. Haven't found an official SD card update for you but I've only done a little bit of searching.
edit: ive only found B19 Nougat full image , but here: https://mega.nz/#F!kYtRAJjJ!5tD1zPpo0nw2tJwhANA9pQ!tNsQhD5Y
download A2017U-7.1.1-B19-Full-326200B1901A2017UV1.1.0B19.zip and extract it and put update.zip in your sd card. boot into stock recovery and use apply update from sd card and select it. hopefully it works and it will downgrade
Click to expand...
Click to collapse
Thank you so much for responding.
So I finally went out and bought an sd card yesterday to try this and I am having no luck.
I tried unzipping the file, but it just creates a duplicate zip file so I simply tried installing the whole package.
Wether I try and install via sd card or via sideload/adb I get the same "installation aborted" message.
This is so frustrating. All I want is to root again! I'm trying to get this phone to last me as long as I can before replacing it.
Doing this all on a Mac, fyi. Not sure if that changes things. Since we're not using EDL or Axon7toolkit I assumed it doesn't matter, but there is a lot that I don't know.
Thanks for any help that you're able to provide!
alajoy said:
Thank you so much for responding.
So I finally went out and bought an sd card yesterday to try this and I am having no luck.
I tried unzipping the file, but it just creates a duplicate zip file so I simply tried installing the whole package.
Wether I try and install via sd card or via sideload/adb I get the same "installation aborted" message.
This is so frustrating. All I want is to root again! I'm trying to get this phone to last me as long as I can before replacing it.
Doing this all on a Mac, fyi. Not sure if that changes things. Since we're not using EDL or Axon7toolkit I assumed it doesn't matter, but there is a lot that I don't know.
Thanks for any help that you're able to provide!
Click to expand...
Click to collapse
If it's saying that error then it's probably not letting you downgrade.
Also this might be slightly more difficult since you're in a Mac. Can you get access to a windows machine at all? This is why I hate macs
Teet1 said:
If it's saying that error then it's probably not letting you downgrade.
Also this might be slightly more difficult since you're in a Mac. Can you get access to a windows machine at all? This is why I hate macs
Click to expand...
Click to collapse
So what would be the reason that it wouldn't let me downgrade?
I've always used a mac and always managed to find an answer. Sure, toolkits don't work, but using fastboot and adb and doing it that way always has. Now suddenly no fastboot and I'm screwed... I don't really have access to a windows pc.
I just find it hard to believe that it's simply not possible on a mac.
alajoy said:
So what would be the reason that it wouldn't let me downgrade?
I've always used a mac and always managed to find an answer. Sure, toolkits don't work, but using fastboot and adb and doing it that way always has. Now suddenly no fastboot and I'm screwed... I don't really have access to a windows pc.
I just find it hard to believe that it's simply not possible on a mac.
Click to expand...
Click to collapse
Yeah fastboot screen was removed in newer versions. But that's at a software level of the phone. On your computer, the adb and fastboot commands are universal. It's usable on Mac, Linux and windows. The tools used for the phone like miflash or axon7tool are made for windows though and you kinda need those to fix bricked phones. There's a way to force push the twrp image into the recovery partition via adb but I don't know what the name of the recovery partition is
@alajoy: You can give yourself access to a fake Windows on your Mac. It's called a virtual machine. VirtualBox is one free software that can do this. Pretty easy to use, you install a virtualized Windows that you can boot into. Then you can run all Windows-based tools out there. It's also easy to share a USB port with the VM. Then flashing tools can access it. I run Linux as my main OS on a Sager gaming laptop, this is how I flash my A7 and Samsung phones. It just works, and reliably. I do also have a real Windows 10 installed on a partition on the same PC, but that is only for gaming and I never, ever allow it to connect to the Internet.
@Teet1: The literal name of the recovery partition is exactly that, recovery. And that is what most Android devices call it, regardless of manufacturer. It doesn't matter whether it is TWRP or ZTE stock recovery, the name is the same. It can be accessed via the paths:
/dev/block/platform/soc/624000.ufshc/by-name/recovery
/dev/block/bootdevice/by-name/recovery
/dev/block/sde14
On other devices the path may be different (but the 2nd example above will work for most), but the name is usually the same.
AnonVendetta said:
@alajoy: You can give yourself access to a fake Windows on your Mac. It's called a virtual machine. VirtualBox is one free software that can do this. Pretty easy to use, you install a virtualized Windows that you can boot into. Then you can run all Windows-based tools out there. It's also easy to share a USB port with the VM. Then flashing tools can access it. I run Linux as my main OS on a Sager gaming laptop, this is how I flash my A7 and Samsung phones. It just works, and reliably. I do also have a real Windows 10 installed on a partition on the same PC, but that is only for gaming and I never, ever allow it to connect to the Internet.
@Teet1: The literal name of the recovery partition is exactly that, recovery. And that is what most Android devices call it, regardless of manufacturer. It doesn't matter whether it is TWRP or ZTE stock recovery, the name is the same. It can be accessed via the paths:
/dev/block/platform/soc/624000.ufshc/by-name/recovery
/dev/block/bootdevice/by-name/recovery
/dev/block/sde14
On other devices the path may be different (but the 2nd example above will work for most), but the name is usually the same.
Click to expand...
Click to collapse
By name i meant the path, are you sure that's the path for our device? I tried that once and it was not that. Either way he is able to do it
@Teet1: Yeah, I'm sure, but not on all 3 paths. /dev/sde14 may be correct or not, depending on firmware/boot stack that is installed (or the presence of a vendor partition, which might change the paths). But the other 2 should be as I listed.
Just open a root file manager and see for yourself. I use Total Commander, which also shows symbolic links (the one with "bootdevice" in the path is really just a symlink to 624000.ufshc). Getting the recovery path from the example with "bootdevice" in the name should also work on almost any device running Android, and will generally point to the recovery partition. You can see the paths in TWRP too, but TWRP doesn't show symlink (but you should be able to see them if you use the right commands in any terminal, like TWRP's terminal).
Hi, sorry if this is the wrong place or wrong format. I want to share with others that I got treble_experimentations running on this phone.
I though this phone was the same as the Logic L55B which has a Unisoc SC9832E, but that seems to be wrong as it contains an MT6739 chipset. It took me a very long time to figure this out, and I didn't find any precise instructions online, despite the final steps not being complicated.
I got this phone very cheaply with the USA Lifeline Affordable Connectivity Program. It came stocked with advertisements and was very unresponsive and glitchy. So, it is gratifying to unlock it and install a community-maintained ROM, as it's possible many people are stuck with it.
I performed these steps. I do not know if they are all necessary
1. i enabled developer mode and OEM unlocking
2. on a system with mtkclient, i ran mtk e metadata,userdata,md_udc and mtk da seccfg unlock as documented at https://www.hovatek.com/forum/thread-40300.html . i did not need to install any kernel patches or anything. note: mtkclient can also be used to take factory images from the phone, or backup the super partition before flashing.
3. booted phone and ran adb reboot fastboot to get into user-space fastbootd mode. normal fastboot won't flash the logical system partition.
4. downloaded an arm32_binder64-ab image from https://github.com/phhusson/treble_experimentations/releases and extract with xz. i used v415 vanilla. edit: i recommend v414 as v415 was never stabilized. newer images are at https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-List
4b. Optional: If the image was larger than the vanilla image, then space needed to be freed. fastboot delete-logical-partition product accomplished this.
5. wiped old system image with fastboot erase system and flashed new with fastboot flash system imagename.img as documented at https://www.xda-developers.com/flash-generic-system-image-project-treble-device/ . I did not need to touch the secure boot partition nor do anything extra.
6. performed mtk e userdata again to resolve occasional conflicts from booting the phone to reboot into fastbootd
The phone is now super snappy, no ads, very responsive, but of course with the vanilla image one must manually install any apps of interest.
It looks like flashing could also be done via the boot rom by working with the super partition.
It seems really helpful to try connecting phones to tools like mtkclient just in case they happen to speak the same protocol. Additionally there is a lot of information in adb shell getprop and a little in fastboot getvar all, but basically I spent the whole day persistently websearching, looking for similarities and possibilities, and trying things, until I found an avenue that worked.
With the some work contacting Hot Pepper, gpl kernel sources and such could be acquired.
fuzzyTew said:
Hi, sorry if this is the wrong place or wrong format. I want to share with others that I got treble_experimentations running on this phone.
I though this phone was the same as the Logic L55B which has a Unisoc SC9832E, but that seems to be wrong as it contains an MT6739 chipset. It took me a very long time to figure this out, and I didn't find any precise instructions online, despite the final steps not being complicated.
I got this phone very cheaply with the USA Lifeline Affordable Connectivity Program. It came stocked with advertisements and was very unresponsive and glitchy. So, it is gratifying to unlock it and install a community-maintained ROM, as it's possible many people are stuck with it.
I performed these steps. I do not know if they are all necessary
1. i enabled developer mode and OEM unlocking
2. on a system with mtkclient, i ran mtk e metadata,userdata,md_udc and mtk da seccfg unlock as documented at https://www.hovatek.com/forum/thread-40300.html . i did not need to install any kernel patches or anything. note: mtkclient can also be used to take factory images from the phone, or backup the super partition before flashing.
3. booted phone and ran adb reboot fastboot to get into user-space fastbootd mode. normal fastboot won't flash the logical system partition.
4. downloaded an arm32_binder64-ab image from https://github.com/phhusson/treble_experimentations/releases and extract with xz. i used v415 vanilla.
4b. Optional: If the image was larger than the vanilla image, then space needed to be freed. fastboot delete-logical-partition product accomplished this.
5. wiped old system image with fastboot erase system and flashed new with fastboot flash system imagename.img as documented at https://www.xda-developers.com/flash-generic-system-image-project-treble-device/ . I did not need to touch the secure boot partition nor do anything extra.
6. performed mtk e userdata again to resolve occasional conflicts from booting the phone to reboot into fastbootd
The phone is now super snappy, no ads, very responsive, but of course with the vanilla image one must manually install any apps of interest.
It looks like flashing could also be done via the boot rom by working with the super partition.
It seems really helpful to try connecting phones to tools like mtkclient just in case they happen to speak the same protocol. Additionally there is a lot of information in adb shell getprop and a little in fastboot getvar all, but basically I spent the whole day persistently websearching, looking for similarities and possibilities, and trying things, until I found avenue that worked.
With the some work contacting Hot Pepper, gpl kernel sources and such could be acquired.
Click to expand...
Click to collapse
Yes, please continue this work, And if there are any other links Please let me know. Looking for info on the Scepter 8 tablet as well, That would be Awesome. Thank you for your time & efforts.
did you use either magisk or TWRP to flash? Do you know if any other system images are compatible or if uploading a UI theme is necessary? Is it still functional for you now? thnx
I searched for the Scepter 8 and found there is an existing thread covering that device, which also has information on working with Hot Pepper the corporation.
Zalg said:
did you use either magisk or TWRP to flash? Do you know if any other system images are compatible or if uploading a UI theme is necessary? Is it still functional for you now? thnx
Click to expand...
Click to collapse
As I mentioned in the first post, I used just mtkclient and fastboot to flash. I suspect TWRP could be made to work. I don't know much about magisk yet. mtkclient is at https://github.com/bkerler/mtkclient . In my opinion the mtkclient code does not sufficiently respect a principle called DRY to maintain it effectively, but at least it is open source and a normative project to communicate with mediatek firmware. mtkclient can be used to extract factory images or flash new partitions, among many other things.
mtkclient speaks a protocol that could possibly work from a phone as well as a desktop. the same is likely true of fastboot. i imagine people have not implemented that yet.
I suspect any treble-based image should work, but I don't really know as I'm new to these things. Making a non-treble image work could mean getting the GPL kernel sources from Hot Pepper which they are legally obligated to provide in their action of distributing a linux-based android phone in the USA.
I don't know what uploading a UI theme is; do other flashing processes require this? I didn't need to do this.
The phone is still working for me but has gotten much slower and glitchier after use; still not as bad as with the factory image, though. I haven't poked at its innards since I made the original post. I suspect it needs a treble_experimentations upgrade by now, or soon, as the revision I am running was a prerelease at the time.
@fuzzyTew, I'm following the same instructions, but mtkclient is giving me this output repeatedly:
I also don't know how to enter BROM mode. I looked at the guide you attached with no avail as the key combos don't work.
```
Port - Hint:
Power off the phone before connecting.
For brom mode, press and hold vol up, vol dwn, or all hw buttons and connect usb.
For preloader mode, don't press any hw button and connect usb.
If it is already connected and on, hold power for 10 seconds to reset.
```
Any fixes?
Try the things in the output you pasted please. Thank you for trying the device setup.
fuzzyTew said:
Try the things in the output you pasted please. Thank you for trying the device setup.
Click to expand...
Click to collapse
I did, but it still isn't working. I'm also using a Chromebook that is using Crostini (linux) and the device doesn't get recognized at all. Probably a Chromebook issue tbh
The phone briefly offers a serial port when it is powered, which mtkclient looks for (the brief serial port should show up in dmesg kernel logs). You could also try running it as root.
You can also see if your device is recognised by an official Mediatek flasher if you find a version your system can run, or ask the communities around mtkclient.
It looks like Crostini doesn’t provide direct access to devices. You would need a system that does, or to poke a hole in the crostini container somehow, or to flash the phone a different way. As mentioned in the first post I found that way to enable fastboot from https://www.hovatek.com/forum/thread-40300.html after a lot of searching from my non-containerized linux system.
Ok. Yea, I probably would. Dang it that sucks. Ehh, I'm sure I'll get access to an actual PC or something that would actually work.
fuzzyTew said:
Hi, sorry if this is the wrong place or wrong format. I want to share with others that I got treble_experimentations running on this phone.
I though this phone was the same as the Logic L55B which has a Unisoc SC9832E, but that seems to be wrong as it contains an MT6739 chipset. It took me a very long time to figure this out, and I didn't find any precise instructions online, despite the final steps not being complicated.
I got this phone very cheaply with the USA Lifeline Affordable Connectivity Program. It came stocked with advertisements and was very unresponsive and glitchy. So, it is gratifying to unlock it and install a community-maintained ROM, as it's possible many people are stuck with it.
I performed these steps. I do not know if they are all necessary
1. i enabled developer mode and OEM unlocking
2. on a system with mtkclient, i ran mtk e metadata,userdata,md_udc and mtk da seccfg unlock as documented at https://www.hovatek.com/forum/thread-40300.html . i did not need to install any kernel patches or anything. note: mtkclient can also be used to take factory images from the phone, or backup the super partition before flashing.
3. booted phone and ran adb reboot fastboot to get into user-space fastbootd mode. normal fastboot won't flash the logical system partition.
4. downloaded an arm32_binder64-ab image from https://github.com/phhusson/treble_experimentations/releases and extract with xz. i used v415 vanilla. edit: i recommend v414 as v415 was never stabilized. newer images are at https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-List
4b. Optional: If the image was larger than the vanilla image, then space needed to be freed. fastboot delete-logical-partition product accomplished this.
5. wiped old system image with fastboot erase system and flashed new with fastboot flash system imagename.img as documented at https://www.xda-developers.com/flash-generic-system-image-project-treble-device/ . I did not need to touch the secure boot partition nor do anything extra.
6. performed mtk e userdata again to resolve occasional conflicts from booting the phone to reboot into fastbootd
The phone is now super snappy, no ads, very responsive, but of course with the vanilla image one must manually install any apps of interest.
It looks like flashing could also be done via the boot rom by working with the super partition.
It seems really helpful to try connecting phones to tools like mtkclient just in case they happen to speak the same protocol. Additionally there is a lot of information in adb shell getprop and a little in fastboot getvar all, but basically I spent the whole day persistently websearching, looking for similarities and possibilities, and trying things, until I found an avenue that worked.
With the some work contacting Hot Pepper, gpl kernel sources and such could be acquired.
Click to expand...
Click to collapse
I have the followed the steps and everything seems like it went as described. But phone only boots to fastboot. For a brief second you see a screen popup but then goes black and to fastboot. Any ideas thanks in advance
Hello new to the forum I'm interested in flashing a custom ROM to my HP serrano pepper, looking for help getting started just now ran into this site look forward to learning more about the procedure