yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 3 7.0 Android Development] mai77:
excellent !

:laugh::laugh::laugh:

smashing ! for us T-110 users the day has finally come !

KING of "planet T-110", the dev Sir paziusss

gave us a non-bootlooping custom recovery !

we now can handily

root (straight from within TWRP, works like a charm)

flash customs roms (well there are only 2 for T110: Criskelo and stock debloated)

above all: make nandroid backups & restore them

just flash the recov with ODIN 3.09, see pic attached :
[Galaxy Tab 3 7.0 Android Development] mai77:
http://xdaforums.com/showpost.php?p=60707541&postcount=2

in TWRP, if u do a "advanced wipe" and wipe "internal storage" too (all is tagged except "MicroSD"), then that will kill the bloody bloatware installer that will otherwise spam ure storage with sh!tty apk's after fresh stock ROM or Criskelo ROM install (as part of most branded versions) .

I guess u get the bloated stuff back when flashing full OS with ODIN.

I found however, that Criskelo deletes TWRP. You would have to reinstall TWRP. Instead I chose to kill Criskelo which was OK but slightly bloated, I felt.
[Galaxy Tab 3 7.0 Android Development] mai77:
I run this TWRP , no prob so far. excellent T110 feel.

:D
[Galaxy Tab 3 7.0 Android Development] mai77:
recovery.fstab safestrap

[FONT=Courier New]/boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot
/system ext4 /dev/block/platform/msm_sdcc.1/by-name/system
/data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata
/cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache
#/misc emmc /dev/block/platform/msm_sdcc.1/by-name/misc
/recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery
/efs emmc /dev/block/platform/msm_sdcc.1/by-name/efs flags=backup=1;display=EFS
/external_sd vfat

/dev/block/mmcblk1p1
/dev/block/mmcblk1

/usb-otg vfat

/dev/block/sda1
/dev/block/sda flags=removable;storage;display=USB-OTG[/FONT]

https://raw.githubusercontent.com/T...samsung_lt02ltetmo/android-4.4/recovery.fstab

fstab of the lt02ltetmo, the expensive NON-LITE Tab 3 7"

it may apply to our T110 as well.

what about safestrap ? :cool:

http://blog.hash-of-codes.com/how-to-safestrap

http://xdaforums.com/tags.php?tag=safestrap
[Galaxy Tab 3 7.0 Android Development] sushil888:
take abow

:angel: ur great

nodobt abt that ur something special dev...

feeling happy for 110 users

njoy
[Galaxy Tab 3 7.0 Android Development] Dudash:
Am I the only one confused as to why this is such a big deal? I've been using the 2.7.0.1 version of TWRP for the T110 from here for over a year and have yet to experience a bootloop or problem of any kind.
[Galaxy Tab 3 7.0 Android Development] mai77:
funny

well did anyone report successful use of that recov earlier ? :rolleyes:

clearly PhilZ recov is bootlooping and no one suggested a replacement. :crying:
[Galaxy Tab 3 7.0 Android Development] paziusss:
You're right here. Bootloop problem only happens if you tell your device to go to recovery (via adb reboot recovery, or with programs like quickboot). If you boot in recovery with buttons combo you'll never see a bootloop cause the tablet doesn't know it boots recovery. The only real scenario you'll find a bootloop is after a factory reset, because It will trigger a reboot-recovery like command and custom recoveries don't handle this. I didn't try to change this from userspace (I know some phones have a /misc partition with BCD data inside, but Tab3 don't). Instead I built a kernel from stock sources which triggers "recovery-done" at every reboot.
[8125, K-JAM, P4300, MDA Vario General] yzf750:
Well I didnt even do it on a rom flash. All I did was start installing MS net compact on my mda since I needed it to run a new program. As it was installing I hit the camera button while setting it on the desk by mistake and the screen slowly faded out to black. MDA wont restart now, wont even power on and I cant even get to the bootloader mode using the power button and camera button. GRRRRRRRRRRR Any ideas?
[8125, K-JAM, P4300, MDA Vario General] bwesty:
completely discharged battery?
[8125, K-JAM, P4300, MDA Vario General] yzf750:
no, fully charged. I said screw it and took a circuit board out of a busted screen mda I had laying around that I bought for 20 bucks off a guy. Of course the volume tab was broke off the slider in that one so now I dont have a way to use the slider. You just cant win I quess. It least it boots fine with the other board in it. Anyone know of a fix for a broke volume slider?
[8125, K-JAM, P4300, MDA Vario General] Junner2003:
Take off the battery for half an hour or so, then try to start the WIZ again afterwards!

While removing the battery hold the power button and continiue to hold it for 30 seconds after you removed the battery! Leave the device without the battery for at least 30 minutes!

When placing the battery back in to the device hold the power button before doing so and keep holding the power button while putting in the battery. Wait a few seconds when done and try then to power on the device!

If nothing happends press and hold the CON button on the left together with the VOICE DIAL button on the right and make a reset while holding those buttons.

Let me know if it worked!
[8125, K-JAM, P4300, MDA Vario General] gonchi:
Do I have a brick too

:( I tryied to install a rom and after following all the instructions I made a hard reset then my phone stay's in the boot screen without continuing!!; my question is do I have a brick or there's a way out!!

thanks

Gonzalo

:confused:
[Galaxy Note 4 Q&A, Help & Troubleshooting] MEGAX91:
use TWRP.
[Sony Xperia M] ajithalbus:
i've Tried to Compile Kernel for my Xperia m ( nicki ) but , i get this error

root@livewire:/media/stuffs/sw/work/android/kernel/android_kernel_sony_msm8x27-cm-12.0# ARCH=arm CROSS_COMPILE=/media/stuffs/sw/work/arm-eabi-4.4.3/bin/arm-eabi

- make nicki

make: execvp: /media/stuffs/sw/work/android/kernel/android_kernel_sony_msm8x27-cm-12.0/scripts/gcc-wrapper.py: Permission denied

HOSTCC scripts/basic/fixdep

/bin/sh: 1: scripts/basic/fixdep: Permission denied

make[2]: *** [scripts/basic/fixdep] Error 126

make[1]: *** [scripts_basic] Error 2

make: *** No rule to make target `nicki'. Stop.

Im not using Ubuntu , is the error due to that ? Pls help
[Sony Xperia M] Razvan:
Hi there,

Please wait until mods will move this thread to the device specific forum http://xdaforums.com/xperia-m/help

Stand by
[Sony Xperia M] adi2500:
Try "sudo make nicki"
[Xoom Q&A, Help & Troubleshooting] QA Bot:
Q&A for [Recovery] ClockworkMod Touch Recovery 6.0.2.7 (20130124)

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [Recovery] ClockworkMod Touch Recovery 6.0.2.7 (20130124). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Xoom Q&A, Help & Troubleshooting] FrEaK@ZoiD !!!:
Thx
[LG Optimus G Pro] yakovpol:
Hi folks,

it seems there's a number of those with hard bricked e98x devices. The only real solution so far is a JTAG service which often is not an option.

Unfortunately, this device though great is not so widely spread as many others, that's may be the reason why HEX file is not publicly available and you can do nothing with (as seen in Linux)

05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

on APQ8064T device (turning your device into SDCARD mode). The only chance I see so far is booting from external microSD card what you can achieve (probably) by forcing your CPU to alternate boot sequence.

Surprisingly, there's Service Manual available in Internet. It is marked as preliminary. It has interesting information about internal design of LG-E980, including data for boot configuration.

And here comes where more help needed. I personally do not have much skills and time to understand it from first glance. If some guidance and help added, I belive it's possible to accomplish the goal.

What I understand so far (please correct if it's mistake):

(1) According to the manual (page 208) the GPIO_87 is connected to 10K resistor R6023 which normally has TRUE for secure boot there;

(2) It is safe to connect CPU side of this resistor to the ground, 10K is enough to keep safe the transistor it is conneced to (Boot Config diagram on the same page);

(3) The location of R6023 is shown on page 240;

(4) This should change the boot sequence.

I want to clarify the matter even before connecting my oscillograph in. If the motherboard is blown, I loose any interest in the project, and I do not want that :)

Any comments are welcome.
[LG Optimus G Pro] yakovpol:
Just in case

Just in case
[LG Optimus G Pro] FarkFung:
now??
[LG Optimus G Pro] darkspr1te:
R6011 to GPIO_50 = BOOT_CONFIG_0_1_6

R6007 to GPIO_4 = BOOT_CONFIG_0_1_6

R6023 to GPIO_87 = BOOT_CONFIG_0_1_6

Shorting either side to GND via a 1k resistor should not cause any harm.

I am going to take a stab in the dark and the say 0_1_6 of the boot config is bit 0/1/6 of the boot chart, E:V:A's documentation into bootloaders should allow you to match the boot order chosen.

EDIT My PDF viewer didnt show the chart at first, displayed here for speed

Config 1 Config 0
0 0 EMER. BOOT(SDC3 FOLLOWED BY USB HS)
0 1 SDC3 FOLLOWED BY SDC1
1 0 SDC3 FOLLOWED BYSDC2
1 1 SDC1 (eMMC, DEFAULT)
Config 6
0 Secure Boot
1 Fast Boot

Secure boot can be controlled via GPIO or QFUSE, if QFUSE is used then gpio options wont matter even if stilll present on the board. Early models may have not had the qfuse blown until the device had been proven which may mean some devices will load a hex file no problem and others wont. (educated assumption)

if you are using a oscilloscope then you should watch these GPIO's at power up and also record your DMESG for changes in the PID/VID of the device,

use this code to see a live view of DMESG when devices are sending their PID/VID

sudo tail -f /proc/kmsg

use CTRL+C to stop.

I've looked into some of the sources that would have been supplied to the manufacturer for them to develop with and there is options for them to alter the fail to boot behavior except the CPU PBL, this is why having no bootloader at all might work where having a failed bootloader wont.

I suggest also try other HEX files, not all are made equal.

darkspr1te
[LG Optimus G Pro] yakovpol:
darkspr1te, many thanks for your reply!

In fact, CPU side of the diagram shows the exact name for the signals:

R6007 to GPIO_4 = BOOT_CONFIG_6

R6011 to GPIO_50 = BOOT_CONFIG_1

R6023 to GPIO_87 = BOOT_CONFIG_0

I did not notice all except GPIO_87: search through PDF file found only horizontally oriented text.

As for HEX files, I tried ALL that I could find, one by one.
[LG Optimus G Pro] darkspr1te:
Ok, progress, sort of. We now know that R6007 is the BOOT_CFG_6 bit, aka fastboot/secure boot. This could still be controlled by a qfuse or they may have shorted to gnd this point making it secure, removing the resistor to gnd and replacing with one to 1.8v/3.3v would always force fastboot.

you should find this on the diagram and board (sorry , time my side is limited)

measure this resistor to ground with device powered . The same for the others once you have found them.

EDIT:- Manual says they are powered from Q6000, so check for the actual precence of R6007, if it's missing then that gpio does not get power and boots in secure mode not fastboot.

darkspr1te
[LG Optimus G Pro] yakovpol:
darkspr1te, thanks again.

In fact, I checked opposite to CPU sides of R6007, R6011, R6023: resistors really exist and all are connected together to the Drain of Q6000 (exactly like on the scheme in the manual). So Q6000 controls the signal on all three of GPIOs. It means it shoud have False in normal conditions.

I am still in preparations to the actual power on. I do not have a lab and some materials (like 1K resistors) needed.

What I think is most difficult for now is that all resistors are on the back side of the motherboard, faced to the screen. I do not know how to deal with that, I want to keep screen attached during the try.
[LG Optimus G Pro] darkspr1te:
For most of the repair nothing will show on the screen, all the interaction is done via USB, the device will function without it for your purpose.

As we know that Q6000 drain is connected to our GPIO we can assume that on power up before the cpu is taken out of reset then power will be applied.

darkspr1te
[LG Optimus G Pro] yakovpol:
FM Radio

One more thought.

It is known that manufacturer disabled the FM radio. If someone knows which pins exactly should be disconnected from the ground, that would be nice to check if there's any chance to use them for radio. This is U29001 chip, pages 221 and 235. I see a number of pins with name starting FM_...

FM_LNAVSS = B2

FM_PLLVSS = B3

FM_LNAVCOVDD = A1

FM_VCOVSS = A2

FM_PLLVDD = A3

Who knows the meaning of them? I see that all VSS ones are grounded, including those for Bluetooth. The question is about A1 and A3.

PS Tomorrow or on day after tomorrow I'll be hopefully able to try power on.
[LG Optimus G Pro] darkspr1te:
VSS often means ground on IC's, VDD is power for IC's

PLL is Phase Locked Loop, this often refers to a antenna tunner,

at a Guess B2,B3,A2 goto ground, A1, A3 to power.

The diagram confirms this, A1,A3 get power from VDD_LN,

B1 is labled FM_RFIN, at a guess FM antenna IN, this normal is connected to headphones via some components(not sure exactly what parts)

You would need to not only check to see if the rquired hardware is there but also have access to the API/chip to switch on the FM input then decode it via the I2C audio channel which will mean changes to the kernel (trust me there, i had same issue with a Rockchip device with FM chip)

NOTE: the page 235 shows the BGA pinouts, not all may be connected on the board.

darkspr1te
[LG Optimus G Pro] yakovpol:
QFUSE is not used!

Some good news here.

After some preparations I finally tried to boot the motherboard with putting BOOT_CONFIG_6 to TRUE. And I could get

USB HID v1.11 Device [HID 05c6:f006]

as a result. But it doesn't stay such, it enumerates once again to 05c6:f006, then switches to 05c6:f008 and remains so.

What I did is:

Unfortunately, I do not have soldering iron tidy and small enough for putting a wire on a resistor which provides BOOT_CONFIG_6 for the CPU. So I simply took a piece of wire sodered to a resistor 1K and connected two pins on sides. While I was holding pins connected to + and CPU side of the resistor, my wife connected a USB. At the same time I was watching

watch -n1 "lsusb | grep 05c6"

and

tail -f /var/log/kern.log

What I found: 1) the battery should be attached in order to get 05c6:f006; 2) pins are not sharp enough, needles should be used; 3) I should probably change the signal on other BOOT_CONFIG_0 and BOOT_CONFIG_1 to have it booting from external SD-card.

The questions: should I hold BOOT_CONFIG_6 on TRUE during all process long, or it will be enough for a few seconds? Or should I press some buttons during the moment when I have 05c6:f006?

As for the Antenna input of U29001 MDM9215M (FM_RFIN, B1), it is next to the edge/side of chip. Theoretically it is possible to connect there a wire, because there's a gap in between motherboard and the chip. But I'm sure special tools needed here and sides are covered by glaze.
[LG Optimus G Pro] yakovpol:
Seems to be no profit in f006

Service manual shows quite tricky booting sequence. I loose hope it this approach :(

What I found is hardware/software solution Octoplus/Octopus. It has surprisingly much info included, mentioning no-JTAG booting problem solution by their software with single TP used on the motherboard. I attach here the way it is described.

By doing so I did not notice any enumeration after releasing the TP.

Encouraging fact is there exists non-JTAG (almost software-only) solution .

EDIT: I realised that TP is for hard hard brick, when no 9008 device comes up via USB on boot.
[LG Optimus G Pro] darkspr1te:
That TP could be the DAT0 test point which stop the device from actually detecting a EMMC flash and will cause it to only follow the PBL. can you give me some timings on when the device switches USB VID/PID, like 1 sec on 9006, two on 9006.

The boot happens the moment the device see's power, normally for just getting the cpu up the usb power is enough although a few times i found that was not enough and had to use battery but that may have been usb port (front are poor for power) or the desktop itself.

as the boot path is emmc - sdcard - pbl in that order, if you notice that only changing one of the boot_0/1 skips the first boot option which is emmc so only one need to be targeted, see captive dev thread on unbrickable mod to get the basic idea of that , i think i posted that link a few posts back.

darkspr1te
[LG Optimus G Pro] yakovpol:
To be continued

Long story short: I was very busy because of my work/obligations and did not write here in April.

I needed the phone much, so I tried to find an appropriate technician where I live now. I gave the phone to him, and he requested US$80 for repair. I refused and took the phone back. Then I realized that that technician used JTAG and phone became hard hard brick (100% dead, no 9008 state or any other sign of life). Removing lot of fluxing material I discovered short circuit between two JTAG contacts. I removed it and the phone came back to the hard brick state. Meanwhile I purchased Medusa Box (along with shipping and taxes it cost me US$128) and used it for so called USB repaire (the software knows HEX and all other things needed to work with e980's APQ8064T QDL mode, no JTAG needed). The phone came back to life.

I would sniff USB bus during communication with the phone in QDL mode and continue finding a way to boot it from sdcard. And I want to get FM radio working.
[LG Optimus G Pro] yakovpol:
A chance to get HEX file

Recently I had to use testpoint on the motherboard to enter QDL mode again. I took the opportunity to sniff USB traffic while using Medusa box for restoring the bootloader, so I hope in the PCAP files I have HEX file is present. If someone wants to help me to extract it, please let me know with a private message or give me a hint how to do it.
[XDA Assist] sharkmobile:
How to make Custom ROM for Samsung Galaxy S3?

Skype: djole.email
[XDA Assist] sharkmobile:
Samsung Galaxy S5 to S3

If i download Samusng Galaxy S5 ROM can i install it on Samsung Galaxy S3 i mean port or switch?
[XDA Assist] Razvan:
No you can't.

I founded some tutorial for your request please see bellow:

[GUIDE]Porting Any Custom Roms[Fastest method][Update for porting MIUI Kitkat]

You can ask directly in this threads.

Good luck
[Verizon Samsung Galaxy S III] cesium:
Apologize if this has been answered, I quickly looked through the relevant sections and stickies and came away confused.

I currently have a Verizon S3 that has an unlocked bootloader and is still on 4.1.2 (some debloated stock ROM). I'd like to update it to a newer version of Android, but do not want to get rid of the unlocked bootloader. From what i've read, that means I cannot flash any TW 4.4 ROMs.

I'm confused as to whether I can flash any of the following:

- a TW 4.3 ROM, e.g., http://xdaforums.com/showthread.php?t=2591895

- an AOSP 4.4 ROM, e.g., http://xdaforums.com/showthread.php?t=2400577

I have no interest in upgrading to lollipop fwiw

Thanks!

EDIT: thanks a lot, installed the TW 4.3 ROM with no issues :)
[Verizon Samsung Galaxy S III] kidhudi:
yes

and

yes
[Verizon Samsung Galaxy S III] ShapesBlue:
Your one of the very few who are still on 4.1.2 on this phone

Sent from my Nexus 5
[Verizon Samsung Galaxy S III] cesium:
Heh I cracked the screen on it when 4.3 was still a dream, so I gave it to my parents to use wifi-only. For their use (basically chromecast and traveling abroad) 4.1.2 sufficed, but I thought some sort of updated OS would be nice from a security perspective.
[Galaxy S6 Edge Q&A, Help & Troubleshooting] vivelafrance:
Hi guys,

I'll receive my S6 Edge in about 3 weeks. Quick question please:

I'm hesitating to root it however, I'll probably want to install a new official ROM (phone i'll receive is from Vodafone but I want a generic Lollipop one).

Is it possible to install a generic Android 5 ROM via Odin via a PC and not root the phone at all?

thnx
[Galaxy S6 Edge Q&A, Help & Troubleshooting] Reb0rn:
Holy **** man... You talk the talk but you defenetly don't walk the walk.

What I'm trying to say is that its way to early to even talk about these things.

First of, we got root but NO custom roms. I don't even know if we have a custom recovery out yet... My guess is no.

And custom Original Samsung ROMs we will have in due time (like Omegaroms and alike)

But custom CM12/AOSP will not happen any where near this half year if ever as Exynos is closed source and most of it has to be hack built. So forget stability too...

Just understand this first before even considering buying the s6 or s6 edge.
[Galaxy S6 Edge Q&A, Help & Troubleshooting] vivelafrance:
I don't think you understood my question here...

I NEVER talked about a custom ROM!! I want to ditch the vodafone ROM and install a generic BAU ROM instead which WILL be available very soon on samfirmware website. And even if it's not available in the next few weeks, it doesn't matter, my question is generic and could fit ANY phones really.

My question is: is it possible to install a BAU ROM without rooting the phone?

Simple, not sure how to explain it further
[Galaxy S6 Edge Q&A, Help & Troubleshooting] Reb0rn:
Ah I get you now. Sorry.

What you are talking about is "unbranding". Yeah that should be easy.

You don't need to be rooted to be able to flash a stock unbranded ROM.
[Galaxy S6 Edge Q&A, Help & Troubleshooting] vivelafrance:
YES! You actually found the word I was looking for and should have used: unbranding! haha SORRY

Yeah, I too thought that I didn't need ROOT to change ROMs if I do it via ODIN and a PC, but I wasn't sure

thnx again!
[Galaxy S6 Edge Q&A, Help & Troubleshooting] mocsab:
Actually it is very dangerous (from what I Have been told) to flash any stock firmware via ODIN on any phone except the model it was intended for - that could and probably would brick your phone - IF it was able to flash at all - which is highly unlikely.

I don't know everything - and many here know a lot more than I do - but from what I have read and been told by others smarter than ME _ NEVER try to flash a rom via odin on your phone unless it was specifically made for your model.

Good luck - I hope you find what you what you are looking for.
[Galaxy S6 Edge Q&A, Help & Troubleshooting] vivelafrance:
I would obviously take the unbranded ROM that is specifically made for my phone version and model... :)
[Galaxy Note 4 Q&A, Help & Troubleshooting] asif.malick:
How to port N910F roms to N910C? What is procedure to port Note 4 roms to different varianta?
[Galaxy Note 4 Q&A, Help & Troubleshooting] Ghassen07:
I search for that since i got my note 4 exynos 3 years ago but i didn't find answer only brick my phone after installation with different variant rom i notice that the port rom for snapdragon version is always perfect and better then the exynos on note 4 i found a rom called red dragon rom on sm n910f is amazing and had a note 7 camera and nougat system ui if anyone can help i will be very thankful because i have no answer for that
[T-Mobile LG G3] cmlucht:
ok story, as of this month whenever I called any one I had to reboot my phone so that they could hear me, if I didn't the person I was calling would just keep saying hello.

well the problem is with the ok Google from any screen setting it is messing up the calls on phone and Bluetooth.

go to Google settings,> search & now,> voice,> ok Google detection,> turn off the from any screen and reboot.

after that problems with calls should be gone.
[T-Mobile LG G3] scaleaton:
Hopefully this works. Thanks! How did you come up with this?