Database Develop

[CLOSED] Kwongger's Nvidia Shield Toolkit NOW CLOSED! NO UPDATES! NO SUPPORT! :/

Kwongger's NVIDIA SHIELD All-In-One- Toolkit​
An All-In-One Kit for our beloved Nvidia Shields.
Provides Unock, Recovery, Root, and Relock!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SORRY NO DL...
THE TOOL IS DISCONTINUED!​

CHANGELOG
...

And this is mine!
Videos will come in the future!
HAHA. I LOVE the disclaimer! "Unless your device starts shooting lasers. Then that's all me".
I seriously got a good laugh out of that!

red triangle in recovery
step 4 which should install super su gives a red triangle..Might want to try this on yours when you get one. thanks for trying..

brian13206 said:
step 4 which should install super su gives a red triangle..Might want to try this on yours when you get one. thanks for trying..
Click to expand...
Click to collapse
Make sure you're booted into android... All it does is adb push the supersu.zip And walk you through the rest.

to be fair
I realized I sounded a little snide.. that wasn't my intention... The red triangle goes away by itself once you unplug the cable.. not sure why but it isnt a brick. one thing I realized on the github solution is you have to put those rootmaster files in the file where you keep your adb files.. (it doesn't mention that) I should also mention that your 1 click did install a recovery as it was supposed to.. thanks again

brian13206 said:
I realized I sounded a little snide.. that wasn't my intention... The red triangle goes away by itself once you unplug the cable.. not sure why but it isnt a brick. one thing I realized on the github solution is you have to put those rootmaster files in the file where you keep your adb files.. (it doesn't mention that) I should also mention that your 1 click did install a recovery as it was supposed to.. thanks again
Click to expand...
Click to collapse
Did you try booted into android?
In the kit you start everything in android

It put the SuperSU zip in my download folder.

I saw that screen.. when I hit :"install" it went to red triangle...

brian13206 said:
I saw that screen.. when I hit :"install" it went to red triangle...
Click to expand...
Click to collapse
NO BOOTLOADER!!!
A post above confirmed that it is working!
If you still have issues, copy and paste the file and go from there

sigh...YES BOOTLOADER.. after I got red triangle I redid root with the github solution and all went well. I'm rooted all is well.. I wasn't trying to point fingers I just posted what happened to me. I'm sure no one will get the red triangle just me...Good luck in your endeavors

brian13206 said:
sigh...YES BOOTLOADER.. after I got red triangle I redid root with the github solution and all went well. I'm rooted all is well.. I wasn't trying to point fingers I just posted what happened to me. I'm sure no one will get the red triangle just me...Good luck in your endeavors
Click to expand...
Click to collapse
Dude. Really???????????
DO NOT START IN BOOTLOADER!!!!!
My method DOES NOT WORK THAT WAY.

Kwongger said:
Dude. Really???????????
DO NOT START IN BOOTLOADER!!!!!
My method DOES NOT WORK THAT WAY.
Click to expand...
Click to collapse
You're instructions CLEARLY say to be booted into Android...

wwjoshdew said:
You're instructions CLEARLY say to be booted into Android...
Click to expand...
Click to collapse
Thanks for the back up
I was getting kind of frustrated, I'll check his past posts... May be a sad attempt at a Troll.

wwjoshdew said:
It put the SuperSU zip in my download folder.
Click to expand...
Click to collapse
brian13206 said:
I saw that screen.. when I hit :"install" it went to red triangle...
Click to expand...
Click to collapse
I am guessing you are referring to the "Install" option in green text in wwjoshdew's 1st picture. Is that correct?
EDIT
Kwongger said:
Dude. Really???????????
DO NOT START IN BOOTLOADER!!!!!
My method DOES NOT WORK THAT WAY.
Click to expand...
Click to collapse
In reality it should not matter IF the Shield is already in bootloader mode or not. the only thing it does by already being in android is make it a little easier for people by not needing to enter bootloader mode by hand. There are alot of good reason to know how to do just that. as far a writing a batch script to automate the process there are options that can be used to check if the device is in fastboot or booted to android. I don't have them memorized, and don't have time to look them up right now.

chevyowner said:
I am guessing you are referring to the "Install" option in green text in wwjoshdew's 1st picture. Is that correct?
EDIT
In reality it should not matter IF the Shield is already in bootloader mode or not. the only thing it does by already being in android is make it a little easier for people by not needing to enter bootloader mode by hand. There are alot of good reason to know how to do just that. as far a writing a batch script to automate the process there are options that can be used to check if the device is in fastboot or booted to android. I don't have them memorized, and don't have time to look them up right now.
Click to expand...
Click to collapse
I adb push the file, so you have to be in Android.

Kwongger said:
I adb push the file, so you have to be in Android.
Click to expand...
Click to collapse
IF you are referring to the supersu.zip it does even need to be on the device to be installed. You can also use "adb push" in recovery, the catch here is if the device you push to is not mounted when pushing the file, the file will not be useable after it is mounted.
That is what the command "adb sideload" is for.
From the CWM main menu you go to install zip>install zip from sideload.
the command would be written in a batch file like this assuming the zip will be in the same folder as the batch script. "adb sideload supersu.zip"
If you are talking about the recovery is a better idea IMO to flash that from recovery.

chevyowner said:
IF you are referring to the supersu.zip it does even need to be on the device to be installed. You can also use "adb push" in recovery, the catch here is if the device you push to is not mounted when pushing the file, the file will not be useable after it is mounted.
That is what the command "adb sideload" is for.
From the CWM main menu you go to install zip>install zip from sideload.
the command would be written in a batch file like this assuming the zip will be in the same folder as the batch script. "adb sideload supersu.zip"
If you are talking about the recovery is a better idea IMO to flash that from recovery.
Click to expand...
Click to collapse
hmm... Never thought of that. I'll just stick with my method, IMO it is simpler and I have already plastered ALL OVER to start booted into android, thanks so much for the feedback!
If you have any other suggestions don't hesitate to let me know

hmmm never been accused of being a troll. i realize I should have never posted this. Just to be clear. I wasn't in bootloader when it happened.I was in android. I did step 4..(install su.) when it was finished I went into recovery to check and got the red triangle I stated that it reverted and restarted by itself and I just went and rooted via a different method.( github joshdew vid ) I tried to say that I didn't blame the Op or his 1 click... that I was posting just what happened to ME and that it probably wouldn't happen to anyone else. I even apologized if I was snide in my first post. I have had many smartphones and have never had an issue rooting. Shield was my only hiccup and I started all of this asking for help.

Let me know how the kit is working!!!
PM me any suggestions you have, for new features or for a new Supported device!!!!!!!!!!!
Thanks,
Kwongger

[Q] TWRP 2.5.0.0 Unresponsive

Hello,
I while ago I decided to root my HTC to get some extra stuff. I used a guide on youtube that seemed to be reasonably well made and followed everystep of the process. But before I could root it I had to unlock the bootloader and install TWRP recovery. I got the latest version and proceeded to the next step, where I encountered my problem. After flashing the recovery everything seemed to be well except that my phone wasn't actually rooted. I decided to redo some of the last steps. This is where things get a bit tricky. I have done this quite a while ago (maybe 3-4 months) and don't exactly remember the steps that I repeated but I think I've also flashed TWRP a second time, as well as some other steps. And when it came to the part where I needed to use the recovery I found out that the recovery doesn't work. I can't press anything on the screen, I can however press the lock button and lock the device but when the *slide to unlock* appears it stops working again. I was running out of time and decided to leave it for another time but time has passed and I never really got the time to tinker with it any more since university started and I'm more busy then ever. This has left me with no ability to root or even update my phone.
This brings me to today, when I restored my phone completely forgetting what has happened. It got back to Android 4.1 and I can't do anything about it.
I hope to sort this out and finally root the phone. But even getting rid of TWRP to the original recovery so I could just update my phone would be very helpfull.
Thank you very much.

aleks945 said:
Hello,
I while ago I decided to root my HTC to get some extra stuff. I used a guide on youtube that seemed to be reasonably well made and followed everystep of the process. But before I could root it I had to unlock the bootloader and install TWRP recovery. I got the latest version and proceeded to the next step, where I encountered my problem. After flashing the recovery everything seemed to be well except that my phone wasn't actually rooted. I decided to redo some of the last steps. This is where things get a bit tricky. I have done this quite a while ago (maybe 3-4 months) and don't exactly remember the steps that I repeated but I think I've also flashed TWRP a second time, as well as some other steps. And when it came to the part where I needed to use the recovery I found out that the recovery doesn't work. I can't press anything on the screen, I can however press the lock button and lock the device but when the *slide to unlock* appears it stops working again. I was running out of time and decided to leave it for another time but time has passed and I never really got the time to tinker with it any more since university started and I'm more busy then ever. This has left me with no ability to root or even update my phone.
This brings me to today, when I restored my phone completely forgetting what has happened. It got back to Android 4.1 and I can't do anything about it.
I hope to sort this out and finally root the phone. But even getting rid of TWRP to the original recovery so I could just update my phone would be very helpfull.
Thank you very much.
Click to expand...
Click to collapse
The background information is helpful but you have given us nothing to go on.
Post a fastboot getvar all except remove the imei and serialno?
What are you trying to accomplish? Return to Stock? S-OFF?

majmoz said:
The background information is helpful but you have given us nothing to go on.
Post a fastboot getvar all except remove the imei and serialno?
What are you trying to accomplish? Return to Stock? S-OFF?
Click to expand...
Click to collapse
Tell me what background information do you need and I'll get everything.
The goal is to get a working recovery, which ever one it would be I don't really care. I just want to be able to update the firmware.

reboot into the bootloader. flash the latest twrp for your device using fastboot flash recovery recoverynamehere.zip
profit

jdgreat4 said:
reboot into the bootloader. flash the latest twrp for your device using fastboot flash recovery recoverynamehere.zip
profit
Click to expand...
Click to collapse
If you could give me a more detailed guide I would toatally do that, because I'm pretty noobish when it comes to this kind of stuff.

aleks945 said:
Tell me what background information do you need and I'll get everything.
The goal is to get a working recovery, which ever one it would be I don't really care. I just want to be able to update the firmware.
Click to expand...
Click to collapse
like he said before, post the output of "fastboot getvar all" except your IMEI and SERIALNO
---------- Post added at 11:06 AM ---------- Previous post was at 11:05 AM ----------
aleks945 said:
If you could give me a more detailed guide I would toatally do that, because I'm pretty noobish when it comes to this kind of stuff.
Click to expand...
Click to collapse
do you have adb and fastboot on your computer?
Do you have HTC drivers installed?

alray said:
like he said before, post the output of "fastboot getvar all" except your IMEI and SERIALNO
---------- Post added at 11:06 AM ---------- Previous post was at 11:05 AM ----------
do you have adb and fastboot on your computer?
Do you have HTC drivers installed?
Click to expand...
Click to collapse
I don't know what adb is, sorry. And no I don't, I had to do everything on my friend's laptop because it didn't seem to work on my machine (W8.1 compared to his W7).
Edit. But I do have acces to it pretty much all the time.

aleks945 said:
I don't know what adb is, sorry. And no I don't, I had to do everything on my friend's laptop because it didn't seem to work on my machine (W8.1 compared to his W7).
Click to expand...
Click to collapse
yes better to use windows 7
go ahead and download adb and fastboot from here: http://forum.xda-developers.com/showthread.php?t=2317790
download and install HTC sync from here: http://www.htc.com/us/support/software/htc-sync-manager.aspx
Once installed, uninstall HTC sync but keep the drivers installed
post back when done

alray said:
yes better to use windows 7
go ahead and download adb and fastboot from here: http://forum.xda-developers.com/showthread.php?t=2317790
download and install HTC sync from here: http://www.htc.com/us/support/software/htc-sync-manager.aspx
Once installed, uninstall HTC sync but keep the drivers installed
post back when done
Click to expand...
Click to collapse
The downloads are complete, just waiting on the instalation. The computer is quite old and slow unfortunatelly.
Thank you again
EDIT. Everything is done.

aleks945 said:
The downloads are complete, just waiting on the instalation. The computer is quite old and slow unfortunatelly.
Thank you again
EDIT. Everything is done.
Click to expand...
Click to collapse
ok so connect your phone with he usb cable to the computer, reboot it in bootloader mode (hold power and vol -). in bootloader select "fastboot"
then lauch the adb command prompt and type "fastboot getvar all". post the output here but edit out the imei and serialno before.

alray said:
ok so connect your phone with he usb cable to the computer, reboot it in bootloader mode (hold power and vol -). in bootloader select "fastboot"
then lauch the adb command prompt and type "fastboot getvar all". post the output here but edit out the imei and serialno before.
Click to expand...
Click to collapse
Here it is.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Link since image seems to be really tiny.
http://i.imgur.com/9cZZRA9.jpg

aleks945 said:
Here it is.
Link since image seems to be really tiny.
http://i.imgur.com/9cZZRA9.jpg
Click to expand...
Click to collapse
you can flash twrp 2.6.3.3
download the file and save it in the same folder where you have installed minimal adb and fastboot
then open the command prompt and with the phone in bootloader/fastboot mode enter these commands:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
What do you want to achieve then? Custom rooted rom? stock rooted rom (latest version)? or you simply what to root the rom you currently have?

alray said:
you can flash twrp 2.6.3.3
download the file and save it in the same folder where you have installed minimal adb and fastboot
then open the command prompt and with the phone in bootloader/fastboot mode enter these commands:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
What do you want to achieve then? Custom rooted rom? stock rooted rom (latest version)? or you simply what to root the rom you currently have?
Click to expand...
Click to collapse
Latest stock rooted ram would be the final goal.

aleks945 said:
Latest stock rooted ram would be the final goal.
Click to expand...
Click to collapse
you can flash this rom: http://www.androidrevolution.org/downloader/download.php?file=One_6.09.401.5_odexed.zip
its the stock rom for 6.09.401.5

alray said:
you can flash this rom: http://www.androidrevolution.org/downloader/download.php?file=One_6.09.401.5_odexed.zip
its the stock rom for 6.09.401.5
Click to expand...
Click to collapse
Doesn't my phone have to be rooted to be able to instal another rom?

aleks945 said:
Doesn't my phone have to be rooted to be able to instal another rom?
Click to expand...
Click to collapse
no just flash the rom from twrp recovery then you can root it if you want.

I backed myself into a brick corner and need some guidance

New issue: Live support team helped me flash my device back to stock. And I resume my day.
Eventually notification notified me of an update downloaded and I agree to install, and then it bootlooped on me.
What luck. Anyway what should I do now, technically my system wasn't wiped like before so I should have more options right?

boot into fastboot and flash all the .img files (except persist and recovery) found here https://build.nethunter.com/misc/oneplus3T/partitions/
make sure the files are in the same folder adb is in
the commands are
fastboot flash boot boot.img
fastboot flash system system.img

nicksmizzle said:
boot into fastboot and flash all the .img files (except persist and recovery) found here https://build.nethunter.com/misc/oneplus3T/partitions/
make sure the files are in the same folder adb is in
the commands are
fastboot flash boot boot.img
fastboot flash system system.img
Click to expand...
Click to collapse
Even if I had USB debugging turned off and no OS?
edit: I didn't realize two of those file were 3GB, that said do I flash system and system sparse? Those are system-sized flashes are those two different systems?
And is there a flashing order?

Ivalicenyan said:
Even if I had USB debugging turned off and no OS?
edit: I didn't realize two of those file were 3GB, that said do I flash system and system sparse? Those are system-sized flashes are those two different systems?
And is there a flashing order?
Click to expand...
Click to collapse
if you are in fastboot usb debugging is null. do boot and then system, don't worry about system sparse. boot and then system is the flashing order.

nicksmizzle said:
if you are in fastboot usb debugging is null. do boot and then system, don't worry about system sparse. boot and then system is the flashing order.
Click to expand...
Click to collapse
Do I assume dsp.img is another one I should ignore?
And: error: cannot load 'system.img'
Boot worked fine tho

Flash the stock recovery.img from that link. Then reboot into recovery. Select English, then Install from ADB. This will put you in ADB sideload. Then flash the full OTA zip by using the command adb sideload *name of the file*.
Sent from my OnePlus3T using XDA Labs

dustin_b said:
Flash the stock recovery.img from that link. Then reboot into recovery. Select English, then Install from ADB. This will put you in ADB sideload. Then flash the full OTA zip by using the command adb sideload *name of the file*.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
That sounds helpful but I'm not familiar with the commands.
But before I do, how sure are you will that work before I go for that? What I knew about flashing a new rom didn't help me due to an error, what nicksmizzle told me to do with flashing system in fastboot didn't work, what if tossing TWRP out the window and going back to stock just digs me even deeper in my hole?

Ivalicenyan said:
That sounds helpful but I'm not familiar with the commands.
But before I do, how sure are you will that work before I go for that? What I knew about flashing a new rom didn't help me due to an error, what nicksmizzle told me to do with flashing system in fastboot didn't work, what if tossing TWRP out the window and going back to stock just digs me even deeper in my hole?
Click to expand...
Click to collapse
It won't. The OTA's are made to be installed in stock recovery. You can check the OnePlus 3 community forums if you would like for more information. But installing the OTA on stock recovery is safe. And BTW, I have done it so I'm not just guessing or anything.
Sent from my OnePlus3T using XDA Labs
---------- Post added at 07:19 AM ---------- Previous post was at 07:14 AM ----------
Ivalicenyan said:
That sounds helpful but I'm not familiar with the commands.
But before I do, how sure are you will that work before I go for that? What I knew about flashing a new rom didn't help me due to an error, what nicksmizzle told me to do with flashing system in fastboot didn't work, what if tossing TWRP out the window and going back to stock just digs me even deeper in my hole?
Click to expand...
Click to collapse
Here's a video to kind of give you an idea of what to do. It's not the greatest but it's short. You will have to fastboot flash the stock recovery image first as the video doesn't cover that.
Sent from my OnePlus3T using XDA Labs

dustin_b said:
It won't. The OTA's are made to be installed in stock recovery. You can check the OnePlus 3 community forums if you would like for more information. But installing the OTA on stock recovery is safe. And BTW, I have done it so I'm not just guessing or anything.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
I went ahead and did that, but when I went to ADB sideload, my computer wouldn't recognize the device
and in cmd prompt it just says waiting on device

Ivalicenyan said:
I went ahead and did that, but when I went to ADB sideload, my computer wouldn't recognize the device
and in cmd prompt it just says waiting on device
Click to expand...
Click to collapse
What OS are you on ?
The command "adb devices" should give a device number as return, if not you may need to install an adb-driver on Win-Systems.
HTH,
Axel

s3axel said:
What OS are you on ?
The command "adb devices" should give a device number as return, if not you may need to install an adb-driver on Win-Systems.
HTH,
Axel
Click to expand...
Click to collapse
Windows 7, but don't I already have the drivers if I was able to install twrp or reflash stock recovery?
Also I did a google search but all im getting are adb drivers for nexus. Is there a generic one I can use somewhere?

Ivalicenyan said:
Windows 7, but don't I already have the drivers if I was able to install twrp or reflash stock recovery?
Click to expand...
Click to collapse
Well, when you are in adb sideload mode and the device is plugged in you should be able to see that in the Windows device manager. AFAIK the download mode (fastboot flashing) is different than adb mode and you may indeed need an adb-driver (just google it, its available quite easily on the web).
But before you do so: does "adb devices" return a device number ?

s3axel said:
Well, when you are in adb sideload mode and the device is plugged in you should be able to see that in the Windows device manager. AFAIK the download mode (fastboot flashing) is different than adb mode and you may indeed need an adb-driver (just google it, its available quite easily on the web).
But before you do so: does "adb devices" return a device number ?
Click to expand...
Click to collapse
Nope, thats what I implied in the 1st post without saying so, I said I ad no adb, as in no adb communication between my device and pc. I didnt think adb worked without usb debugging turned on because before I even created the thread I did over the flashing guide I used to install TWRP. devices didn't give me the serial like it did yesterday when I flashed twrp.
and I searched adb sideload opeplus 3 drivers and its just giving me oneplus i isntalled that came with the phone. Unless theres something specific I need, then im probably going to google the wrong thing

Ivalicenyan said:
Nope, thats what I implied in the 1st post without saying so, I said I ad no adb, as in no adb communication between my device and pc. I didnt think adb worked without usb debugging turned on because before I even created the thread I did over the flashing guide I used to install TWRP. devices didn't give me the serial like it did yesterday when I flashed twrp.
and I searched adb sideload opeplus 3 drivers and its just giving me oneplus i isntalled that came with the phone. Unless theres something specific I need, then im probably going to google the wrong thing
Click to expand...
Click to collapse
Sorry, misunderstood you there Well, I have recently used the download from this site for my OP3, so I hope it just works out

s3axel said:
Sorry, misunderstood you there Well, I have recently used the download from this site for my OP3, so I hope it just works out
Click to expand...
Click to collapse
Thanks for the drivers,.
says installation failed on the oneplus after 2-3 minutes

Ivalicenyan said:
Thanks for the drivers,. says installation failed on the oneplus after 2-3 minutes
Click to expand...
Click to collapse
Hmm, strange. Maybe you have a corrupt download ? Can you open the ZIP you downloaded in your first post with 7Zip or something alike ?
If the ZIP file seems fine (BTW, the one I downloaded has a MD5 checksum 0e2b4f9c7e7a1edf533f0d436ba48d95 - opens up OK for me but could not check flashing due to lack of OP3T ) it may help to follow along the instructions on factory resetting that can be found here. Just be careful, this is for OP3. #1 is already covered (given your downloaded ZIP is fine), #2 can be gotten from the link given in Post #2 in this thread.
Then you should hopefully have a clean basis to start from....
Cheers, Axel

s3axel said:
Hmm, strange. Maybe you have a corrupt download ? Can you open the ZIP you downloaded in your first post with 7Zip or something alike ?
If the ZIP file seems fine (BTW, the one I downloaded has a MD5 checksum 0e2b4f9c7e7a1edf533f0d436ba48d95 - opens up OK for me but could not check flashing due to lack of OP3T ) it may help to follow along the instructions on factory resetting that can be found here. Just be careful, this is for OP3. #1 is already covered (given your downloaded ZIP is fine), #2 can be gotten from the link given in Post #2 in this thread.
Then you should hopefully have a clean basis to start from....
Cheers, Axel
Click to expand...
Click to collapse
Got past step #5, it is recongnizing my serial is fastboot devices, but then I got to step #11
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Ivalicenyan said:
Got past step #5, it is recongnizing my serial is fastboot devices, but then I got to step #11
Click to expand...
Click to collapse
OK, so far so good [emoji6] what happens if you type "adb devices" after that?
Gesendet von meinem SM-G935F mit Tapatalk

s3axel said:
OK, so far so good [emoji6] what happens if you type "adb devices" after that?
Gesendet von meinem SM-G935F mit Tapatalk
Click to expand...
Click to collapse

Ivalicenyan said:
Click to expand...
Click to collapse
It seems the daemon ist not running when first giving the command. As it should have started after the first command, what happens if you just repeat the "adb devices" for a second time?
Gesendet von meinem SM-G935F mit Tapatalk

Maze Alpha X Bootloop Problem [SOLVED]

Hello everybody please help me. I tried to Root my phone I unlocked the phone while getting help from “dreambo” then I unlocked the phone and download twrp recovery then when I tried to start phone it only showed me recovery menu sistem was not opening then tried to chech “dreambo” again then i saw a picture (picture 1) there I wrote “fastboot flash recovery boot.alpha.x.img” instead of “fastboot flash boot boot.alpha.x.img” and now phones recovery didnt open and become bootloop it shows logo then turn off (video 1) then i cant able to to put phone into “bootloader mode” . I know this phone doesn’t have stock rom how can i fix this phone ?
dreambo Thread: Root and TWRP 3.2.1 for Maze Alpha X 6/64
(picture 1)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(video 1)​
video link: https://youtu.be/QYMCOQiExMg
Originally Posted
dreambo said:
I am almost sure that you have flashed the recovery image in the boot partition !
You have do that fastboot flash boot recovery.img instead of fastboot flash recovery recovery.img
To have your phone working, just flash the attached boot.img : fastboot flash boot boot.alpha.x.img
Click to expand...
Click to collapse
Edit: Way to solve Problem:
Stive very thanks to my friend after a long time I fixed the phone. In order to do UNBRICK phone download this from link and than put phone into charge than connect phone to computer with usb and open "Flash tool" program than add “MT6757_Android_scatterr.txt” file than put it “Frimware Upgrade” than download and wait until it finished.
Stive87 said:
Unbrick Maze Alpha X 6/64GB only phone is black screen and phone is total brick (format all partition).
https://drive.google.com/file/d/12t3MHsAWBlXyKm_ktJt9GKqZ9sOrFRVi/view
Rom is no official :
System : official rom for Maze Alpha B6/64GB . (! no update after - OTA !!),
boot, logo and recovery is normal (copy from original my phone).
Good luck.
Sorry for bad english, my french ^^
Click to expand...
Click to collapse
Stive87 said:
https://drive.google.com/file/d/12t3MHsAWBlXyKm_ktJt9GKqZ9sOrFRVi/view?usp=drivesdk
full rom V03 6/64GB Rom Ofifcial Stock
https://drive.google.com/file/d/1WjXKj8abnghy_OjfUW5TYkAppjWg0amH/view?usp=sharing
Click to expand...
Click to collapse
Thanks to everyone who helped!!

help please

rafaello21 said:
help please
Click to expand...
Click to collapse
Became interested in this phone since I found a 6/128 model for 160$. If fastboot is failing (maybe because of the different partition size?) I'd go with SPFlashTool: if I remember well phone only need to be swithed off when you start downloading the image, therefore it goes well with bootloping if you choose the right moment

matteo.de-leo said:
Became interested in this phone since I found a 6/128 model for 160$. If fastboot is failing (maybe because of the different partition size?) I'd go with SPFlashTool: if I remember well phone only need to be swithed off when you start downloading the image, therefore it goes well with bootloping if you choose the right moment
Click to expand...
Click to collapse
I bought it 170$ when it was on discount no matter what i do “bootloader mode” not works because of the error that i did and no one helps

rafaello21 said:
I bought it 170$ when it was on discount no matter what i do “bootloader mode” not works because of the error that i did and no one helps
Click to expand...
Click to collapse
That's exactly what I'm saying: SPFlashTool doesn't require your phone to be in fastboot mode, only to be switched of when you plug it in. I had the same problem with an Archos Sense 55S after treying to root it. I wasn't able to enter neither fastboot or recovery mode, therefore I flashed the stock rom with SPFT

matteo.de-leo said:
That's exactly what I'm saying: SPFlashTool doesn't require your phone to be in fastboot mode, only to be switched of when you plug it in. I had the same problem with an Archos Sense 55S after treying to root it. I wasn't able to enter neither fastboot or recovery mode, therefore I flashed the stock rom with SPFT
Click to expand...
Click to collapse
I would do it if i have Stock rom ? i am very disappointed because of bought this phone how is it possible that phone doesnt have stock rom is there any possibility to fix this without stock rom?

rafaello21 said:
I would do it if i have Stock rom i am very disappointed because of bought this phone how is it possible that phone doesnt have stock rom is there any possibility to fix this without stock rom?
Click to expand...
Click to collapse
Which model are you using, the 6/64 or the 6/128?
For the former you can use a TWRP Backup done by @dreambo in order to restore at least the boot and and recovery partition
https://forum.xda-developers.com/maze-alpha/development/recovery-twrp-3-2-1-maze-alpha-x-t3740575
while for the latter a link in this post (https://forum.xda-developers.com/maze-alpha/development/original-rom-t3720714) is given ( eventually as soon as my phone arrives I can dump the image):
Option 1) https://drive.google.com/drive/folde...ZyDQFgygsdkei2
Option 2) http://bit.ly/2GKcmYe

matteo.de-leo said:
Which model are you using, the 6/64 or the 6/128?
For the former you can use a TWRP Backup done by @dreambo in order to restore at least the boot and and recovery partition
https://forum.xda-developers.com/maze-alpha/development/recovery-twrp-3-2-1-maze-alpha-x-t3740575
while for the latter a link in this post (https://forum.xda-developers.com/maze-alpha/development/original-rom-t3720714) is given ( eventually as soon as my phone arrives I can dump the image):
Option 1) https://drive.google.com/drive/folde...ZyDQFgygsdkei2
Option 2) http://bit.ly/2GKcmYe
Click to expand...
Click to collapse
Hi, can i use this to restore my phone? And do you know how? I did a search in the web but didn't fin any solution.

ttl1982 said:
Hi, can i use this to restore my phone? And do you know how? I did a search in the web but didn't fin any solution.
Click to expand...
Click to collapse
Hi ttl1982, before giving an answer I should know what are we talking about. Is it the same phone? And which version? What is the current situation (bootlooping into TWRP, bootlooping into Android)? Even assuming we're still talking about the Maze Alpha X, there are still too much variables!

matteo.de-leo said:
Which model are you using, the 6/64 or the 6/128?
For the former you can use a TWRP Backup done by @dreambo in order to restore at least the boot and and recovery partition
https://forum.xda-developers.com/maze-alpha/development/recovery-twrp-3-2-1-maze-alpha-x-t3740575
while for the latter a link in this post (https://forum.xda-developers.com/maze-alpha/development/original-rom-t3720714) is given ( eventually as soon as my phone arrives I can dump the image):
Option 1) https://drive.google.com/drive/folde...ZyDQFgygsdkei2
Option 2) http://bit.ly/2GKcmYe
Click to expand...
Click to collapse
I have Maze Alpha X 6/64 model. If “bootloader mode” doesnt open how can i install ‘twrp’ ? About Thread article i read everything but my only problem is my phone dont open “bootloader mode”. And only solution is stock rom i think than you need SPFlashTool to install it. Maybe you know better than me how can i install “twrp” without opening “bootloader mode” ? I wrote above why this happened.
I click Power and Vol+ buttons as i show in the video phone turn of but doesn’t open “bootloader mode”

rafaello21 said:
I have Maze Alpha X 6/64 model. If “bootloader mode” doesnt open how can i install ‘twrp’ ? About Thread article i read everything but my only problem is my phone dont open “bootloader mode”. And only solution is stock rom i think than you need SPFlashTool to install it. Maybe you know better than me how can i install “twrp” without opening “bootloader mode” ? I wrote above why this happened.
I click Power and Vol+ buttons as i show in the video phone turn of but doesn’t open “bootloader mode”
Click to expand...
Click to collapse
No, even in the case you just want to boot into TWRP (and be able to use one of the backups provided in that post) you need to access fastboot mode. during bootlooping does your PC find the device with the "adb devices" command (namely, as soon as your phone boots up you'd spam this command via terminal)?

matteo.de-leo said:
Hi ttl1982, before giving an answer I should know what are we talking about. Is it the same phone? And which version? What is the current situation (bootlooping into TWRP, bootlooping into Android)? Even assuming we're still talking about the Maze Alpha X, there are still too much variables!
Click to expand...
Click to collapse
Hi, Thanks for your quick response. I will share some more info like you asked.
- Phone: Maze Alpha X
- Version: 6GB RAM/128GB Storage
- Current situation: It won't start at all (when connected to Windows PC i get the 'USB device not recognized' error, so it does see something)
My idea is the following:
- Install recovery with SPK flashtool
- Restore with backup (i have this from another thread) or the system dump.
The above does not work because i do not have the correct preloader file (so SPK flash tool does recognize the phone?).
ADB is not recognizing the phone, so it can't be done that way (as far as my knowledge goes).
I asked Maze several times to provide me the original rom but i get zero response, no matter on what channel i ask them.

matteo.de-leo said:
No, even in the case you just want to boot into TWRP (and be able to use one of the backups provided in that post) you need to access fastboot mode. during bootlooping does your PC find the device with the "adb devices" command (namely, as soon as your phone boots up you'd spam this command via terminal)?
Click to expand...
Click to collapse
I will try but phone turn off and one very quick. Is 1-2 seconds enough for doing what you are saying ? Twrp flash i have to do ? Is there any phone and have similar problem like this ? Can help with help of Video ? And i will try what you said and back to you thanks

ttl1982 said:
Hi, Thanks for your quick response. I will share some more info like you asked.
- Phone: Maze Alpha X
- Version: 6GB RAM/128GB Storage
- Current situation: It won't start at all (when connected to Windows PC i get the 'USB device not recognized' error, so it does see something)
I got this phone from my nephew. He broke it because he flashed the Maze Alpha (not X) 4GB RAM/64GB storage rom on it because he had TWRP bootloops.
My idea is the following:
- Install recovery with SPK flashtool
- Restore with backup (i have this from another thread) or the system dump.
The above does not work because i do not have the correct preloader file (so SPK flash tool does recognize the phone?).
ADB is not recognizing the phone, so it can't be done that way (as far as my knowledge goes).
I asked Maze several times to provide me the original rom but i get zero response, no matter on what channel i ask them.
Click to expand...
Click to collapse
I also wrote them several times about stock rom but they didn’t answer me i think company only think about money. Do we have to throw our phone to garbage because of one wrong thing ? What should i do ?

ttl1982 said:
My idea is the following:
- Install recovery with SPK flashtool
- Restore with backup (i have this from another thread) or the system dump.
Click to expand...
Click to collapse
Yes I was thinking the same. Eventually you do not need to install the recovery, restoring the bootloader should be enough: if the bootloader is already unlocked you can just boot into TWRP and from there restoring the backup previously copied into a SD card.
The above does not work because i do not have the correct preloader file (so SPK flash tool does recognize the phone?).
Click to expand...
Click to collapse
Why do you say you don't have the right one? Did SPFlashTool return you some error?
I asked Maze several times to provide me the original rom but i get zero response, no matter on what channel i ask them.
Click to expand...
Click to collapse
Well AFAIK Maze is completely done, no surprise if they do not answer. I'm reasonably sure that there's a way to dump these files from a working phone, if I'm right I'll try with mine

matteo.de-leo said:
No, even in the case you just want to boot into TWRP (and be able to use one of the backups provided in that post) you need to access fastboot mode. during bootlooping does your PC find the device with the "adb devices" command (namely, as soon as your phone boots up you'd spam this command via terminal)?
Click to expand...
Click to collapse
I tried when I click Power and Vol+ it does bootloop.But the only way to put phone into “bootloader mode” you need SPFlashTool. I dont know what can i do now. When phone was bootlooping i wrote several times “adb devices” but nothing happened

matteo.de-leo said:
Yes I was thinking the same. Eventually you do not need to install the recovery, restoring the bootloader should be enough: if the bootloader is already unlocked you can just boot into TWRP and from there restoring the backup previously copied into a SD card.
I will try this, maybe that works.
Why do you say you don't have the right one? Did SPFlashTool return you some error?
Yes, it says 'status preloader invalid'
Well AFAIK Maze is completely done, no surprise if they do not answer. I'm reasonably sure that there's a way to dump these files from a working phone, if I'm right I'll try with mine
Click to expand...
Click to collapse
That explains a lot. But it is still not acceptable to answer no one imo
---------- Post added at 10:48 PM ---------- Previous post was at 10:34 PM ----------
matteo.de-leo said:
Yes I was thinking the same. Eventually you do not need to install the recovery, restoring the bootloader should be enough: if the bootloader is already unlocked you can just boot into TWRP and from there restoring the backup previously copied into a SD card.
Why do you say you don't have the right one? Did SPFlashTool return you some error?
Well AFAIK Maze is completely done, no surprise if they do not answer. I'm reasonably sure that there's a way to dump these files from a working phone, if I'm right I'll try with mine
Click to expand...
Click to collapse
ttl1982 said:
That explains a lot. But it is still not acceptable to answer no one imo
Click to expand...
Click to collapse
I now get another error when flashing boot.img:
ERROR: STATUS_BROM_CMD_STARTCMD_FAIL

ttl1982 said:
ERROR: STATUS_BROM_CMD_STARTCMD_FAIL
Click to expand...
Click to collapse
As reported by another user on this website: https://forum.hovatek.com/thread-21351.html
The device attempted to power on before SP flash tool could flash files to it
Click to expand...
Click to collapse
Phone must be plugged (while switched off) to the USB port after having given the Download order to SP
---------- Post added at 09:38 PM ---------- Previous post was at 09:34 PM ----------
By the way, it seems that this very website (in particular here https://forum.hovatek.com/thread-468.html) hosts a guide to dump a Mediatek firmware SPFlashTool compatible, together with the necessary files, but guess what? You need to register in order to download them, something that I'll definitely do if it just lets me

ttl1982 said:
I now get another error when flashing boot.img:
Click to expand...
Click to collapse
Which boot.img you chose ?
matteo.de-leo said:
Phone must be plugged (while switched off) to the USB port after having given the Download order to SP
Click to expand...
Click to collapse
What should i do exactly to use SPFlashTool ? What alternative ? When I connect my phone to pc it turn off turn on then power volume + and - buttons randomly and than turn on turn off stoped now it looks like this in the picture . Than i checked “adb devices” it says “waiting for devices”. The thing that “dreambo” shared “boot.alpha.x.img” and can i adjust this with SPFlashTool and install it ?

rafaello21 said:
Which boot.img you chose ?
What should i do exactly to use SPFlashTool ? What alternative ? When I connect my phone to pc it turn off turn on then power volume + and - buttons randomly and than turn on turn off stoped now it looks like this in the picture . Than i checked “adb devices” it says “waiting for devices”. The thing that “dreambo” shared “boot.alpha.x.img” and can i adjust this with SPFlashTool and install it ?
View attachment 4518023
Click to expand...
Click to collapse
I have used the exact same boot.img as you did.

[SOLVED] Can't using LGUP now. bootloop with 9008 mode. (V409N)

Hello!
I unlocked the bootloader first.
However, after rebooting, the twrp failed to flash.
and I got a message to re-lock the bootloader.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After that, I checked several guides and tried.
but now, never can't boot and can't use LGUP.
Any method to restore stock rom via 9008 mode? please help.
PS :
I think download mode is also broken.
Please let me know if there's any way to recover the download mode.

1688_ said:
Hello!
I unlocked the bootloader first.
However, after rebooting, the twrp failed to flash.
and I got a message to re-lock the bootloader.
View attachment 5211369
After that, I checked several guides and tried.
but now, never can't boot and can't use LGUP.
View attachment 5211375
View attachment 5211379
Any method to restore stock rom via 9008 mode? please help.
PS :
I think download mode is also broken.
Please let me know if there's any way to recover the download mode.
Click to expand...
Click to collapse
I'd suggest looking at this thread. Also, the screen telling you the bootloader is unlocked is normal, when you have a device that has it unlocked, you *always* see it when you boot up.
cheers

AsItLies said:
I'd suggest looking at this thread. Also, the screen telling you the bootloader is unlocked is normal, when you have a device that has it unlocked, you *always* see it when you boot up.
cheers
Click to expand...
Click to collapse
Very thank you!
but Unfortunately, it didn't work for me.
I forgot what i did, but maybe I modified xbl_a, xbl_b, etc.
and try below method it didn't work, too.
I've touched too many things....
I'd like to know if there's a way to force the use of LG Flash Tool or something like that.

1688_ said:
Very thank you!
but Unfortunately, it didn't work for me.
I forgot what i did, but maybe I modified xbl_a, xbl_b, etc.
and try below method it didn't work, too.
I've touched too many things....
I'd like to know if there's a way to force the use of LG Flash Tool or something like that.
Click to expand...
Click to collapse
Follow this post. (Don't speak Spanish so have no idea what the above video is doing, can't help there).
Essentially, when you flash an image to a partition it doesn't belong in, you run the risk of overwriting into nearby partitions (because image is bigger than partition size). If you do that, then the only solution is what's in the post above. It basically restores the entire device using qfil. Because when you start overwriting partitions (and possibly the partition table), there's no way of knowing what is messed up and what isn't.
cheers

AsItLies said:
Follow this post. (Don't speak Spanish so have no idea what the above video is doing, can't help there).
Essentially, when you flash an image to a partition it doesn't belong in, you run the risk of overwriting into nearby partitions (because image is bigger than partition size). If you do that, then the only solution is what's in the post above. It basically restores the entire device using qfil. Because when you start overwriting partitions (and possibly the partition table), there's no way of knowing what is messed up and what isn't.
cheers
Click to expand...
Click to collapse
thank you !!
I'll try this right now and report

you
AsItLies said:
Follow this post. (Don't speak Spanish so have no idea what the above video is doing, can't help there).
Essentially, when you flash an image to a partition it doesn't belong in, you run the risk of overwriting into nearby partitions (because image is bigger than partition size). If you do that, then the only solution is what's in the post above. It basically restores the entire device using qfil. Because when you start overwriting partitions (and possibly the partition table), there's no way of knowing what is messed up and what isn't.
cheers
Click to expand...
Click to collapse
You are my hero!! So many thank you!!
I've only tried 3 and 4.
download mode has come alive.
btw, why my v40 has fail to install twrp?
my system is LMV409N(SKT)
Maybe I should give up custom rom for a while.
many thanks!!!

1688_ said:
you
You are my hero!! So many thank you!!
I've only tried 3 and 4.
download mode has come alive.
btw, why my v40 has fail to install twrp?
my system is LMV409N(SKT)
Maybe I should give up custom rom for a while.
many thanks!!!
Click to expand...
Click to collapse
good that it worked. Follow this link and in the folder find boot_20n_magisk.img and use it (assuming you're on kor 20n), use qfil to flash it to boot_a and b.
It has both magisk and twrp in it. Remember, after flashing it in qfil (save original first of course), you need to hold vol - and pwr for a few seconds (until u hear windows chime meaning disconnect), to exit qfil.
But! and this is important, we don't want the device to boot, we want to go directly to recovery. So keep both buttons pressed but when LG logo appears, release pwr and then re-apply it, which then goes to recovery.
in recovery, u have to format data, then reboot recovery and flash dm_verity.
cheers

AsItLies said:
good that it worked. Follow this link and in the folder find boot_20n_magisk.img and use it (assuming you're on kor 20n), use qfil to flash it to boot_a and b.
It has both magisk and twrp in it. Remember, after flashing it in qfil (save original first of course), you need to hold vol - and pwr for a few seconds (until u hear windows chime meaning disconnect), to exit qfil.
But! and this is important, we don't want the device to boot, we want to go directly to recovery. So keep both buttons pressed but when LG logo appears, release pwr and then re-apply it, which then goes to recovery.
in recovery, u have to format data, then reboot recovery and flash dm_verity.
cheers
Click to expand...
Click to collapse
Thank you very much for your follow-up.
I succeeded in entering the twrp.
But I got screen asking password, there's default password or something?

1688_ said:
Thank you very much for your follow-up.
I succeeded in entering the twrp.
But I got screen asking password, there's default password or something?
View attachment 5213013
Click to expand...
Click to collapse
There's no password, you just cancel out of that but be sure to do the 'swipe' to make it modifiable. The key after that is to format data, then reboot recovery and flash dm_verity, then encryption won't exist and no longer asked for pw.
cheers

AsItLies said:
There's no password, you just cancel out of that but be sure to do the 'swipe' to make it modifiable. The key after that is to format data, then reboot recovery and flash dm_verity, then encryption won't exist and no longer asked for pw.
cheers
Click to expand...
Click to collapse
OK, Thank you!!
I followed the guide below and no more password message!!
How to use decrypted stock by @Xsavi : https://forum.xda-developers.com/lg-v40/how-to/guide-twrp-data-access-stock-t3970149
I think everything's finally settled.
I'll try my best to enjoy the v40 now.
Thank you so much for your help.
many many thank you!!!!!!!